Skip to main content
Glama
cameronrye

AT Protocol MCP Server

by cameronrye

search_posts

Search posts on AT Protocol by text query, author, language, date range, and more. Filter results by top or latest sorting with authentication required.

Instructions

Search for posts on AT Protocol. Supports text search with various filters including author, language, date range, and more. Requires authentication (AT Protocol API changed in 2025 to require auth for search).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qYes
limitNo
cursorNo
sortNolatest
sinceNo
untilNo
mentionsNo
authorNo
langNo
domainNo
urlNo
Behavior2/5

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

With no annotations provided, the description carries full burden. It discloses authentication requirement but omits behavioral traits such as pagination behavior, rate limits, error handling, and whether results are truncated. Minimal transparency beyond basic functionality.

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 sentences with no unnecessary words. First sentence states purpose, second adds crucial auth note. Efficient and front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a complex tool with 11 parameters and no output schema, the description is incomplete. It fails to explain pagination, output structure, and behavior of unspecified filters. Leaves significant gaps for agent understanding.

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 description coverage is 0%, so description must compensate. It only mentions 'author, language, date range' filters, ignoring 8 other parameters like 'limit', 'cursor', 'sort', 'mentions', 'domain', 'url'. Does not add meaning to most parameters.

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 the verb 'Search' and resource 'posts', explicitly identifying the tool's purpose. It distinguishes from sibling tools like 'discover_trending' by focusing on text search with filters.

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?

The description mentions a critical requirement (authentication) but does not provide guidance on when to use this tool versus alternatives like 'get_timeline' or 'discover_trending'. No explicit when-not-to-use or sibling comparisons.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/cameronrye/atproto-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server