Skip to main content
Glama

Mark posts scheduled or posted, and their views

social_posts_update

For each post and platform: scheduled once the founder pressed Schedule, posted with its link once it is live, skipped when the founder left it out, and its views and likes as read in the platform's own studio or insights in the founder's Chrome (routines/posts.md steps 6 and 7). The views lean next week's mix. Free.

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": {
      "updates": "<updates>"
    },
    "name": "social_posts_update"
  }
}

Input Schema

NameRequiredDescriptionDefault
updatesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior4/5

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

Annotations only declare it is a non-destructive write; the description adds the important operational context that views/likes are read from the platform's own studio in the founder's Chrome, and that status reflects an action the founder already took. That explains the data source and the 'free' cost, well beyond the structured fields, though it omits what happens to fields not supplied in an update.

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

Conciseness3/5

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

It is a single dense sentence with tangled conditionals ('posted with its link once it is live') followed by two disconnected fragments, including a bare 'Free.' The status information is front-loaded reasonably, but the structure is narrative rather than scannable.

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

Completeness3/5

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

For a one-parameter batch mutation with no output schema, the definition covers state semantics and metric provenance but leaves the return value, partial-update behavior, and per-item failure handling unexplained. Adequate to call correctly, not adequate to predict results.

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 description coverage is essentially 0% (only the nested id is described), so the description must carry the load; it does clarify the status vocabulary and the views/likes source, but says nothing about the required id/platform pair, the url field's role, or the 1-80 array bounds. Partial compensation only.

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 identifies the resource (posts, per platform) and the specific state/link/metric fields being written, with the three statuses named explicitly. It never states a clean verb like 'update', and the intent has to be pieced together from the conditional phrasing ('scheduled once the founder pressed Schedule...'), which keeps it below a 5.

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

Usage Guidelines3/5

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

It anchors itself to routines/posts.md steps 6 and 7 and implies this is the step-6/7 tool, which is useful routing context. However, it never says when not to use it or names social_posts_save (which the schema's id description points back to) as the creation alternative, so the agent must infer the boundary.

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.