Commonly

Official

Overview Schema Related Servers Discussions Admin

commonly_get_messages

Read-only

Read chat messages from a Commonly pod, including paginated history and complete threads, to review conversations and retrieve context.

Instructions

Read chat messages from a pod. limit is clamped server-side to [1, 50] (default 20). To page into older history, pass the createdAt timestamp of the oldest message as before; the response hasMore flag distinguishes another page from the end of history. Pass threadRootId (a message id) to read one thread — returns the root message plus every reply in that thread, oldest first.

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": {
      "podId": "<podId>"
    },
    "name": "commonly_get_messages"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No
`podId`	Yes
`before`	No
`threadRootId`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.16Nov 13, 2026

TDQS

A3.9/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered; the description adds genuinely useful behavior: server-side clamping of `limit` to [1,50] with default 20, the `hasMore` end-of-history flag, and thread results returned oldest-first. Those are real operational details, but return value shape and error behavior remain unstated, so it lands just above baseline rather than at the top.

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?

Three tight sentences, front-loaded with the core purpose, then paging, then thread mode. No filler and no repetition of the title or schema.

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?

Given there is no output schema, the description usefully discloses the `hasMore` flag and reply ordering, which an agent needs to page and parse correctly. It stops short of describing what a message object contains, but for a four-parameter read tool with read-only annotations, that omission is minor.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage the description carries the burden, and it explains three of four parameters well — `limit`'s clamp and default, `before`'s paging semantics, and `threadRootId`'s message-id meaning and return scope. `podId` is left implicit, which is the only significant gap.

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 opens with a specific verb and resource ("Read chat messages from a pod") and further specifies two modes: chronological reading with paging and single-thread reading. The resource is distinct from siblings like get_posts or get_tasks, though no sibling is named explicitly to sharpen the boundary.

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?

It clearly states how to page into older history (pass the oldest message's createdAt as `before`) and when to use `threadRootId` (to read one thread). What's missing is explicit when-not-to-use guidance or a named alternative for related reads.

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