Skip to main content
Glama

record_x_post

OWNER ONLY — after posting on @NewsGurus, record the post's internal signature. post_url = the x.com status URL; writer_agent / poster_agent = who wrote and who posted it (e.g. Researcher / NG-Reply); text = the exact text that went out; format = brief|reply|quote|video|breaking|scorecard|eod|thread_leg|single|other; source_file = the newsletter path. Returns the weighted character count. Never posts anything. Requires an OWNER-tier API key.

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": {
      "post_url": "<post_url>",
      "writer_agent": "<writer_agent>",
      "poster_agent": "<poster_agent>",
      "text": "<text>"
    },
    "name": "record_x_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYes
formatNosingle
post_urlYes
quoted_idNo
media_kindNonone
source_fileNo
poster_agentYes
writer_agentYes
in_reply_to_idNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the authorization tier, the non-posting read/record nature, and the return value (weighted character count). It is silent on duplicate-record behavior, idempotency, and failure modes, which matter for a record operation.

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?

Access restriction and the critical 'never posts' disclaimer are front-loaded, then parameter semantics are packed into a compact semicolon-delimited run. Nearly every clause carries new information, and there is no filler.

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 9-parameter tool with an output schema present, the description covers the ownership gate, the timing, the core fields, and the return value, so an agent could invoke it correctly. The only shortfall is the three undocumented optional ID/media parameters and unstated behavior on repeated submissions.

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 coverage is 0%, so the description must compensate, and it does for most parameters — clarifying post_url is the x.com status URL, naming writer_agent/poster_agent with concrete examples, and spelling out the allowed format values, which the schema does not enumerate. Three parameters (quoted_id, media_kind, in_reply_to_id) remain undocumented in both places, keeping it below a 5.

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?

The description opens with a specific verb+resource pair ('record the post's internal signature') scoped to a named account (@NewsGurus), and immediately distinguishes the tool from a posting action with 'Never posts anything'. An agent can tell exactly what this does without inspecting the schema.

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 gives explicit sequencing ('after posting on @NewsGurus') and a hard access condition ('OWNER ONLY', 'Requires an OWNER-tier API key'), which is enough to decide whether this tool is callable. It does not name an alternative or say what to do instead if the caller lacks owner tier, so it stops short of full when/when-not guidance.

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.

Resources