Skip to main content
Glama
cameronrye

AT Protocol MCP Server

get_post_context

Read-only

Retrieve full post context including thread, author profile, engagement metrics, and media embeds in one request using optional flags.

Instructions

Get comprehensive post information in a single call. Single post reader: use include* flags for thread, author, engagement, and media. Replaces the former get_thread and extract_media_from_post tools. Works without authentication; richer with auth. Subject to per-tool rate limiting.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
uriYesAT-URI of the post to read (at://...).
includeThreadNoInclude thread context (parent chain, root, and replies). Default true.
includeAuthorProfileNoInclude the post author's full profile. Default true.
includeEngagementNoInclude computed engagement metrics (likes, reposts, replies, rate, age). Default true.
depthNoHow many levels of replies to fetch (0–10, default 6).
parentHeightNoHow many parent posts up the chain to fetch (0–80, default 80).
includeMediaNoExtract media embeds (images, videos, external links, quote posts) from the post. Default false.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
successYesWhether the post context was retrieved.
postYesThe requested post (normalized post view).
threadNoThread context (present when includeThread is true): the immediate parent, the true thread root, the direct replies, and the parent-chain depth.
authorProfileNoThe post author's full profile (present when includeAuthorProfile is true).
engagementNoComputed engagement metrics (present when includeEngagement is true).
mediaNoMedia embeds extracted from the post (present when includeMedia is true).
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint. Description adds behavioral details: works without authentication but richer with auth, subject to per-tool rate limiting, and that it replaces older tools. This provides useful context beyond the annotations, though no contradictions.

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?

Description is front-loaded with the core purpose. Five short sentences each add unique value: purpose, usage pattern, replacement info, auth behavior, and rate limiting. No wasted words.

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

Completeness5/5

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

Given the tool's complexity (7 parameters, 1 required), presence of output schema, and annotations, the description covers key aspects: what it does, how to use flags, auth implications, rate limits, and relationship to previous tools. It is fully sufficient for an agent to invoke correctly.

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?

Schema description coverage is 100%, so the schema fully documents parameters. The description adds value by summarizing the include* flags and noting the default behaviors (e.g., 'Default true' for include flags). It does not repeat all schema details, but the additive context is helpful.

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?

Description clearly states 'Get comprehensive post information in a single call' and 'Single post reader', with specific mention of include* flags for thread, author, engagement, and media. It explicitly replaces former tools get_thread and extract_media_from_post, distinguishing itself effectively from siblings.

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?

Description provides clear context for when to use: 'Get comprehensive post information in a single call' and mentions it replaces previous tools. It also notes authentication options and rate limiting. However, it does not explicitly list when not to use this tool versus other sibling tools like get_author_feed or search_posts, leaving some ambiguity.

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