Skip to main content
Glama

Social0

get_post

Read-onlyIdempotent

Get full details of a single Social0 post by ID, including caption, status, platforms, media, and schedule time.

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_id": "<post_id>"
    },
    "name": "get_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
post_idYesPost ID to retrieve

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is fully covered. The description contributes useful behavioral detail by enumerating the returned content categories (caption, status, platforms, media, schedule time), but says nothing about error behavior for missing IDs, permissions, or rate limits.

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?

One front-loaded sentence with no filler: the resource and lookup key come first, followed by the concrete content returned. Every clause carries information.

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 one-parameter read tool with no output schema, the description supplies the crucial return-content summary the schema cannot. It is nearly complete; only missing-ID/error handling and any access constraints keep it from a 5.

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?

There is a single parameter with 100% schema description coverage and a uuid format, so the schema fully documents it. The description only echoes it as 'by ID' without adding format, lookup semantics, or aliasing information, which matches the baseline 3 for high schema coverage.

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 ('Get full details of a single Social0 post by ID') plus the field categories returned, so an agent can tell this is a point lookup rather than a listing or analytics call. It does not explicitly name a contrasting sibling, which keeps it short of 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?

Usage is only implied: 'by ID' signals you must already know the post identifier, which distinguishes it in practice from list_posts. There is no explicit when-to-use/when-not statement, no mention of get_publish_status as an alternative for status checks, and no guidance on what to do with an unknown ID.

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.