Skip to main content
Glama
cameronrye

AT Protocol MCP Server

batch_action

Idempotent

Apply a single follow, like, or repost action to up to 25 targets in one API call, performing real writes to the network.

Instructions

Batch the same action across up to 25 targets in one call. Supported actions: follow (handles/DIDs), like (AT-URIs), repost (AT-URIs). Requires authentication (app password). Performs real writes (follows/likes/reposts) to the network on the caller's behalf. Subject to per-tool rate limiting.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYesThe action to apply to every target.
targetsYesFor action=follow: handles or DIDs. For action=like/repost: post AT-URIs. 1–25 items.
continueOnErrorNoWhether to keep processing remaining targets after an individual target fails. Defaults to true; set to false to stop at the first failure (unprocessed targets are reported as skipped in the summary).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
successYes
actionYes
resultsYesPer-target outcome {target/uri, success, error?}.
summaryYesCounts: total, succeeded, failed, skipped.
Behavior4/5

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

Discloses real writes to network, authentication need, and rate limiting. Aligns with annotations (idempotentHint=true, destructiveHint=false, openWorldHint=true). Adds context beyond annotations.

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?

Three sentences, each essential: purpose, supported actions and target formats, auth/write/rate limiting. Front-loaded with main capability. No wasted 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?

Covers main aspects: scope, actions, error handling, requirements. Output schema exists (not shown), so return values need not be explained. Minor gap: no mention of response summary structure.

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 covers all parameters (100%). Description adds value by clarifying target formats per action and continueOnError default behavior. Baseline 3, increased for added clarity.

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?

Clearly states verb 'batch', resource 'same action across targets', and scope 'up to 25 targets'. Distinguishes from sibling single-action tools (follow_user, like_post, repost) by grouping multiple identical actions.

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?

Explains when to use (batching multiple same actions) and requirements (authentication, rate limiting). Implicitly excludes single-action tools. Could be explicit about not using for mixed action types.

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