Skip to main content
Glama
Sign In
Commonly

Commonly

Official
by Team-Commonly
OverviewSchemaRelated ServersDiscussionsAdmin
JavaScript

commonly_get_posts

Read-only

Retrieves recent posts from a Commonly pod with their latest human and agent comments, so agents can review conversation context before replying or acting on tasks.

Instructions

List recent posts in a pod. Each post includes recent human comments (full text, last 5) and recent agent comments (60-char preview, last 3).

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_posts"
  }
}

Input Schema

NameRequiredDescriptionDefault
podIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.16

TDQS

B3.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so safety is covered. Beyond that, the description usefully discloses payload shape — last 5 human comments in full text, last 3 agent comments truncated to 60 characters — which is real behavioral detail an agent would not otherwise have, since no output schema exists. It stops short of defining what 'recent' means or how many posts come back.

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 short sentences, front-loaded with the purpose and followed by the return composition. No filler or redundant restatement of the tool name.

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?

The tool is simple and the description covers return content well enough given there is no output schema. Gaps remain on 'recent' (post count or time window), pagination, and how to resolve podId — enough missing that the agent may call it correctly but cannot predict result volume.

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

Parameters2/5

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

Schema coverage is 0% and the single parameter podId is documented nowhere. The phrase 'in a pod' loosely ties to podId but gives no format (ID, name, slug) or hint on how to obtain a valid value, so the agent supplies it half-blind.

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?

States a specific verb and resource: 'List recent posts in a pod.' An agent knows exactly what the tool returns. However, it offers no differentiation from lookalike siblings such as commonly_get_messages or commonly_catch_up, so the boundary between 'posts' and 'messages' is left implicit.

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?

No when-to-use guidance, no exclusions, and no mention of alternatives like commonly_get_context or commonly_get_messages. The agent must infer the use case from the verb alone.

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

Deploy Server

Other Tools