Skip to main content
Glama

Suggest improvements to an article's share post

flypost_suggest_article_share_post_edits
Read-only

Up to 4 short ideas for improving the LinkedIn post that shares an article (the Share panel's suggestions). Saves nothing: apply one with flypost_write_article_share_post (as feedback).

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_suggest_article_share_post_edits"
  }
}

Input Schema

NameRequiredDescriptionDefault
feedbackNoOptional steer for the suggestions.
article_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false; the description reinforces this with 'Saves nothing' and adds genuinely new workflow context by naming the tool that must be used to make a change. It does not discuss output format beyond 'up to 4 short ideas' or any rate/cost behavior, so it is helpful but not exhaustive.

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?

Two compact sentences, front-loaded with the output and followed by the persistence caveat and next step. Every clause carries meaning, though the telegraphic fragment style makes it slightly harder to parse than a full sentence would.

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 simple two-parameter read-only tool with no output schema, the description covers what is produced (up to 4 ideas), that nothing persists, and how to act on results. Only the handling of the feedback parameter and the exact shape of returned suggestions are left implicit.

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?

Schema coverage is 50%: feedback is documented in the schema, article_id is not. The description implies article_id (the article whose share post is being improved) but says nothing about the feedback parameter or how steering alters results. With half the schema documented, the description partially compensates but leaves a gap.

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 gives a concrete verb+resource: producing up to 4 short ideas for improving the LinkedIn post that shares an article, and ties it to the Share panel. It also distinguishes itself from flypost_write_article_share_post, which applies rather than suggests, though the opening noun fragment ('Up to 4 short ideas...') is slightly less direct than a verb-first statement.

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

Usage Guidelines4/5

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

It clearly places the tool in a workflow: generate suggestions here, then apply a chosen one via flypost_write_article_share_post as feedback. That names the downstream alternative and its condition. It stops short of stating when not to use it or how it relates to the other suggestion siblings.

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.