Skip to main content
Glama

Autopilot posts

autopilot_list_posts
Read-onlyIdempotent

Your autopilot's recent posts, newest first, optionally for one character or with one status (pending-approval shows the queue waiting for you), with preview links that expire in six hours.

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": "autopilot_list_posts"
  }
}

Input Schema

NameRequiredDescriptionDefault
statusNo
characterIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), and the description adds a genuinely useful behavioral trait beyond them: preview links expire after six hours, which affects caching/reuse decisions. It stops short of pagination, limits, or default result size.

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 front-loaded sentence covering resource, ordering, filters, and link expiry with no filler. The nested parenthetical makes it slightly dense, but each clause carries real information.

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?

For a list tool with no output schema, the description gives ordering and a link-expiry caveat but omits result volume, pagination, or default behavior when no filter is supplied. That leaves a meaningful gap for an agent deciding whether one call is sufficient.

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%, so the description must carry parameter meaning. It clarifies that characterId scopes to one character and explains the meaning of the pending-approval status value, but the other four enum values (scheduled, posted, failed, rejected) are left to self-explanatory naming with no added meaning.

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 resource (the autopilot's posts) with scope and ordering (newest first) plus optional filters, so an agent knows exactly what it returns. It doesn't explicitly differentiate from any sibling, but no sibling appears to list posts, so confusion risk is low.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Implies usage through the parenthetical that pending-approval 'shows the queue waiting for you', which hints at the approval-review workflow, but there is no explicit when-to-use/when-not or reference to an alternative tool. Guidance is inferable rather than stated.

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