Skip to main content
Glama

Validate post

mynahcast_validate_post
Read-onlyIdempotent

Validate a post against every target channel without saving it.

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": {
      "brandId": "<brandId>",
      "content": "<content>",
      "targets": "<targets>"
    },
    "name": "mynahcast_validate_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
draftNoSave as a draft that keeps the schedule time (nothing is queued); schedule it later with reschedule
titleNo
memoryNo
brandIdYes
contentYes
targetsYes
scheduleNo
submitForApprovalNo

Output Schema

NameRequiredDescriptionDefault
okYes
targetsYes
contentHashYes
wouldRequireApprovalYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / properties / targets / items / properties / provider / enum
      Previous value: -[
      -  "bluesky",
      -  "mastodon",
      -  "telegram",
      -  "discord",
      -  "x",
      -  "linkedin",
      -  "youtube",
      -  "tumblr",
      -  "nostr",
      -  "lemmy",
      -  "misskey",
      -  "slack",
      -  "matrix",
      -  "devto",
      -  "hashnode",
      -  "wordpress",
      -  "listmonk"
      -]New value: +[
      +  "bluesky",
      +  "mastodon",
      +  "telegram",
      +  "discord",
      +  "x",
      +  "linkedin",
      +  "youtube",
      +  "tumblr",
      +  "nostr",
      +  "lemmy",
      +  "misskey",
      +  "slack",
      +  "matrix",
      +  "devto",
      +  "hashnode",
      +  "wordpress",
      +  "listmonk",
      +  "instagram",
      +  "threads",
      +  "facebook"
      +]
  2. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, and 'without saving it' largely restates the read-only guarantee. It adds no context on what gets validated (channel capability limits, duplicate-hook checks, media rules) or whether validation can be expensive or rate-limited.

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?

A single tight sentence with the scope and the non-persistence guarantee front-loaded; nothing is wasted or buried.

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?

This is a heavily nested tool (content/thread/media, per-target overrides, schedule, approval flag) with 13% schema coverage, so a one-line description leaves the agent without the meaning of most inputs. The output schema covers return values, but the input-side explanation is far too thin for this complexity.

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

Parameters2/5

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

Schema description coverage is only 13%, yet the description explains zero parameters — not brandId, content, targets, schedule, submitForApproval, or the per-target override/options objects. With 8 largely undocumented nested parameters, the description does nothing to compensate for the 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?

States a specific verb and resource ('Validate a post') plus two distinctive qualifiers: it checks against every target channel and persists nothing. An agent can distinguish it from get_post/list_posts siblings without reading the schema, though it does not name a save/publish counterpart explicitly.

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?

Usage is only implied — the 'without saving it' clause suggests this is a pre-flight check run before creating or scheduling a post, but the description never states when to call it, when to skip it, or which alternative tool performs the actual save.

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