Skip to main content
Glama

List posts

mynahcast_list_posts
Read-onlyIdempotent

List posts (cursor pagination), filtered by brand, status, channel and time range.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "mynahcast_list_posts"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNo
fromNo
limitNo
cursorNo
statusNo
brandIdNo
channelIdNo

Output Schema

NameRequiredDescriptionDefault
itemsYes
nextCursorYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / properties / items / items / 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, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The only extra behavior the description discloses is cursor-based pagination, which is modest but useful context for iterating results. It says nothing about ordering, result size caps, or what an empty page 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 tight sentence with the resource front-loaded and pagination plus filters appended in a sensible order. No filler, though it is arguably over-compressed given how much parameter detail is missing.

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, so return values need not be explained, and annotations cover the safety profile. Still, for a 7-parameter tool with zero schema descriptions, the definition should at minimum pin down valid status values and date-range behavior; those gaps remain.

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% across 7 parameters, so the description carries real weight; it does name the four filter dimensions (brand, status, channel, time range), mapping to brandId, status, channelId, from and to. However, it leaves 'status' as a free-form string with no indication of valid values, and gives no date-range semantics (inclusive/exclusive, timezone expectations) or limit behavior.

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 verb and resource ('List posts') and adds scope ('filtered by brand, status, channel and time range'), which distinguishes it from single-item siblings such as mynahcast_get_post. It does not explicitly name a sibling, but the list-vs-get distinction is clear from the verb.

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 or when-not-to-use guidance and no named alternative (e.g., mynahcast_get_post_timeline for a single post's history). The filter list implies a browsing/querying use case, but the agent must infer that on its own.

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