Skip to main content
Glama

Write the post that shares an article

flypost_write_article_share_post
Destructive

Have the app write the LinkedIn post that shares an article (the article editor's Share panel), in the project's voice, and save it on the article, replacing any saved one. Pass feedback to revise the saved one. For ideas on improving it without changing it, use flypost_suggest_article_share_post_edits. Or write the post yourself and put it on a draft as usual.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "article_id": "<article_id>"
    },
    "name": "flypost_write_article_share_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
feedbackNo
article_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

The annotations declare destructiveHint=true, and the description supplies the reason: the write replaces any previously saved share post. It also discloses that generation happens in the project's voice and that feedback mutates the saved version rather than creating a new one. It does not mention cost/latency of model generation or what happens if feedback is passed when nothing is saved, so it stops short of full transparency.

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

Conciseness4/5

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

Three short sentences, front-loaded with the primary action before the alternative-tool routing. The parenthetical locating the Share panel is high-value; the closing 'as usual' is the only slightly loose wording.

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

Completeness4/5

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

For a two-parameter mutation with no output schema, the definition covers purpose, mutation semantics (replacement), revision flow, and the suggestion-only alternative. What is missing is minor: whether the generated post text is returned, and error behavior when feedback is supplied without an existing saved post.

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

Parameters4/5

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

Schema description coverage is 0%, so the description must carry the load, and it does for the non-obvious parameter: feedback is defined as revision input applied to the already-saved post, which the bare string schema does not convey. article_id's meaning is only implied by 'save it on the article', but it is unambiguous given the tool name and siblings.

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

Purpose5/5

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

States a specific verb (write) and resource (the LinkedIn post that shares an article), anchors it to a concrete surface (the article editor's Share panel), and distinguishes it from the sibling suggest tool by name. An agent can tell exactly which artifact is produced and where it lands.

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

Usage Guidelines5/5

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

Explicitly covers the three decision paths: call this to write and save, pass feedback to revise an already-saved post, and use flypost_suggest_article_share_post_edits when the user only wants ideas without changing the post. It even names the manual fallback (writing the post yourself onto a draft), leaving little to inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.