Skip to main content
Glama
Sign In

Statuz

by app.statuz
OverviewDiscussionsAdmin

Find an account's replies

posts_lookup
Read-only

An account's own replies to people's posts, once they're there. Finds the replies the account posted (on the network's own site, too) to each of up to 20 posts, in one read of its latest posts: each is null until there is one (or when the post is gone). --since narrows it to replies from then on.

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": {
      "account": "<account>",
      "replyTo": "<replyTo>"
    },
    "name": "posts_lookup"
  }
}

Input Schema

NameRequiredDescriptionDefault
orgNoOrg id (default: your first org)
sinceNoOnly replies from this time on (ISO)
accountYesAccount id, handle or platform name (its default account)
replyToYesTheir posts' links (one read covers them all)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

The annotations already declare readOnlyHint and openWorldHint, and the description adds useful behavior: results are null until a reply exists or when the post is gone, up to 20 posts are handled in one read, and --since narrows results. It does not cover auth or rate limits, but that is not a major gap given the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short, but the opening is a fragment and phrases like 'once they're there' and 'on the network's own site, too' reduce clarity. The content is not wasteful, but the structure is awkward and not ideally front-loaded.

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?

The schema and annotations are rich, and the description supplies key return behavior, including null results for missing replies and batch semantics for up to 20 posts. No output schema exists, so the description could say more about the shape of non-null replies, but it is sufficient for correct invocation.

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 coverage is 100%, so all four parameters are already documented. The description reinforces the replyTo cap and since filtering but adds little meaning beyond what the schema provides, making the baseline score of 3 appropriate.

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?

It states a specific verb and resource: finds the replies an account posted to each of up to 20 posts. That is clear and distinguishable, but it does not explicitly contrast itself with related siblings such as posts_get, posts_search, posts_recent, or posts_list.

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?

The description explains behavior but gives no explicit when-to-use, prerequisites, or named alternatives. The 'one read' and '--since' details are operational hints, not guidance for choosing this tool over related post tools.

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

All Statuz toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources