AT Protocol MCP Server

get_author_feed

Read-only

Retrieve the feed of posts from a specific AT Protocol user by handle or DID. Supports pagination and filtering by post type.

Instructions

Retrieve posts by a specific AT Protocol user. Works without authentication; richer with auth. Lists a specific user's posts. Differs from get_timeline (your home feed) and search_posts (query-based search). Subject to per-tool rate limiting.

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": {
      "actor": "<actor>"
    },
    "name": "get_author_feed"
  }
}

Input Schema

Name	Required	Description
`actor`	Yes	Handle or DID of the account whose posts to list.
`limit`	No	Max posts per page (1–100, default 50).
`cursor`	No	Pagination cursor from a previous response.
`filter`	No	Which of the author's posts to include (default posts_with_replies).

Output Schema

Name	Required	Description
`success`	Yes	Whether the request succeeded.
`posts`	Yes	Posts by the specified author for this page.
`cursor`	No	Opaque cursor for the next page; absent when there are no more results.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.6.2Jun 23, 2026
- removedInput schema / additionalProperties
```
Removed value: -false
```
Addedv0.6.0Jun 11, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint. The description adds value by stating the tool works without authentication and is subject to rate limiting, which are behavioral traits beyond what annotations provide.

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?

The description is four sentences, each serving a distinct purpose: purpose, auth behavior, scope, and differentiation with rate limit. It is front-loaded and contains no unnecessary words.

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 the 4 parameters (100% schema coverage) and presence of an output schema, the description covers necessary context: auth behavior, differentiation, and rate limiting. It is largely complete, though could mention pagination briefly, but cursor is in schema.

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 baseline is 3. The description does not add additional meaning to any parameter beyond what is already in the schema. It mentions 'Lists a specific user's posts' but that is about tool scope, not specific parameter semantics.

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?

The description clearly states 'Retrieve posts by a specific AT Protocol user,' using a specific verb and resource. It also distinguishes from siblings 'get_timeline' and 'search_posts' by explaining their different purposes.

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?

The description provides context on authentication behavior ('Works without authentication; richer with auth') and explicitly contrasts with two sibling tools. It does not give explicit when-not-to-use guidance but sufficiently implies usage context.

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