Skip to main content
Glama

Get post timeline

mynahcast_get_post_timeline
Read-onlyIdempotent

Every delivery attempt for a post, with platform response codes.

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": {
      "postId": "<postId>"
    },
    "name": "mynahcast_get_post_timeline"
  }
}

Input Schema

NameRequiredDescriptionDefault
postIdYes

Output Schema

NameRequiredDescriptionDefault
attemptsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds that results include platform response codes, which is genuinely useful context about the content returned, but says nothing about ordering, pagination, or what an empty timeline means.

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?

A single short sentence, front-loaded with the resource and scope, with no filler. It is efficient but so terse that it borders on under-specification.

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?

An output schema exists and annotations are rich, so return shape and safety need not be described. However, for a diagnostic tool the definition gives no hint about ordering, completeness of attempts, or when to reach for it over mynahcast_get_post, leaving a modest gap.

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 0%, but there is only one parameter (postId), whose name and uuid format make its meaning self-evident; the description only reinforces it with 'for a post'. It adds essentially no new semantics such as whether failed attempts are included or how postId is obtained.

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 names a specific resource ('every delivery attempt for a post') and scope ('every'), which distinguishes it from the single-post lookup mynahcast_get_post. It never explicitly names that sibling, so differentiation is inferred rather than stated.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no mention of alternatives such as mynahcast_get_post, and no stated preconditions (e.g., the post must have been published or attempted). The agent must infer the use case from the phrase 'delivery attempt'.

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