Skip to main content
Glama

Read a host's recent posts

read_recent_posts

Read the 20 recent posts from a host to check whether a timed-out post was published before retrying.

Instructions

Read the 20 most recent posts from one of your hosts, newest first. Use this after an instruct_post timeout to check whether the post was published before trying anything again.

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": {
      "host_id": "<host_id>"
    },
    "name": "read_recent_posts"
  }
}

Input Schema

NameRequiredDescriptionDefault
host_idYesThe host's positive integer id (from list_hosts).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.15.3
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / host_id / maximum
      Added value: +9007199254740991
  2. Addedv0.11.0

TDQS

A4/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the burden. It does disclose two useful behavioral traits: the result is capped at 20 items and ordered newest first, and the verb 'Read' implies a non-mutating operation. It says nothing about permissions, whether a host with fewer than 20 posts simply returns fewer, or what fields a post contains — a meaningful gap given there is no output schema.

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?

Two sentences, no filler. The capability statement comes first and the operational guidance second, which is the right front-loading for an agent scanning definitions.

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 single-parameter read tool with no annotations and no output schema, the description covers the essentials: what is returned, how many, and in what order, plus the recovery scenario. The only shortfall is that it never hints at the shape of a post object, which the agent must discover at call time.

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?

Only one parameter and schema coverage is 100%; the schema already explains host_id is a positive integer sourced from list_hosts. The description adds no further meaning about the parameter, so the baseline of 3 applies.

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?

States a specific verb (Read), a specific resource (the 20 most recent posts from one of your hosts), and adds scope details (count cap and newest-first ordering). The resource is clearly distinct from siblings like read_chat_history or read_host_photos, so an agent can route correctly without opening 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?

Explicitly names the trigger scenario — after an instruct_post timeout — and what to do with the result (check whether the post was published before retrying). That ties it directly to a sibling. It does not cover other legitimate uses (e.g., general browsing of a host's posts) or state when not to use it, keeping it short of a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.