Skip to main content
Glama

share_to_published

Publish articles to your Tiny Tiny RSS feed by creating entries in the Published source with title, URL, and content.

Instructions

创建一篇文章到已发布 (Published) 源中

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYes文章标题
urlYes文章 URL
contentYes文章内容

Implementation Reference

  • Tool registration and handler definition for 'share_to_published'. It wraps the client's 'shareToPublished' method.
    server.tool(
      "share_to_published",
      "创建一篇文章到已发布 (Published) 源中",
      {
        title: z.string().describe("文章标题"),
        url: z.string().url().describe("文章 URL"),
        content: z.string().describe("文章内容"),
      },
      async (params) => {
        try {
          await client.shareToPublished(params);
          return ok("分享到已发布成功");
        } catch (e: unknown) {
          return fail(`分享失败: ${(e as Error).message}`);
        }
      },
    );
  • Actual implementation of the shareToPublished method in TtrssClient, which sends the request to the API.
    async shareToPublished(params: {
      title: string;
      url: string;
      content: string;
    }): Promise<{ status: string }> {
      return this.request("shareToPublished", params);
    }
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden of behavioral disclosure. While '创建' (create) implies a write operation, the description doesn't disclose important behavioral traits like required permissions, whether the operation is idempotent, what happens if the article already exists, or any rate limits. It provides minimal behavioral context beyond the basic action.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence that states the tool's purpose without any wasted words. It's appropriately sized for a tool with clear parameters and no complex behavioral nuances to explain.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a write operation tool with no annotations and no output schema, the description is incomplete. It doesn't explain what happens after creation (success/failure responses, return values), doesn't mention any constraints or side effects, and provides minimal behavioral context. The description should do more to compensate for the lack of structured metadata.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 100% schema description coverage, the input schema already documents all three parameters (title, url, content) with Chinese descriptions. The tool description adds no additional parameter semantics beyond what's in the schema, so it meets the baseline for high schema coverage without adding value.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('创建一篇文章' - create an article) and the target resource ('到已发布 (Published) 源中' - to the Published source), providing a specific verb+resource combination. However, it doesn't distinguish this tool from potential sibling tools like 'update_article' or 'get_article' that might also work with articles.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites, when-not-to-use scenarios, or differentiate from sibling tools like 'update_article' or 'search_articles' that might also handle article-related operations.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/aooiuu/ttrss-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server