analyze_account

Read-only

Analyze a Bluesky account's engagement metrics, network health, or posting strategy. Use read-only operations to get performance insights, graph analysis, and recommendations.

Instructions

Analyze a single account along one dimension. Requires authentication (app password). Read-only: performs no writes. One account-analysis tool: pick a dimension. For topic/search-based influencer discovery use find_influential_users instead. Subject to per-tool rate limiting.

Input Schema

TableJSON Schema

Name	Required	Description
`actor`	No	Handle or DID to analyze. Defaults to the authenticated user when omitted.
`dimension`	Yes	Which analysis to run: 'engagement' = recent-post performance; 'network' = follower/following graph health; 'strategy' = posting recommendations.
`limit`	No	How many recent posts to sample for engagement analysis (1–100, default 50).
`maxSampleSize`	No	How many connections to sample for network analysis (default per old behavior).
`includeReplies`	No	Engagement: include replies in the sampled author feed (default true).
`includeFollowers`	No	Network: sample the followers graph (default true).
`includeFollows`	No	Network: sample the follows graph (default true).
`analyzePosts`	No	Strategy: how many recent posts to analyze (10–100, default 50).
`includeTimingAnalysis`	No	Strategy: include best-posting-time analysis (default true).
`includeTopicAnalysis`	No	Strategy: include topic/keyword analysis (default true).

Output Schema

TableJSON Schema

Name	Required	Description
`success`	Yes	Whether the analysis succeeded.
`dimension`	Yes	Which analysis was run.
`actor`	No	network/strategy dimensions: the DID or handle that was analyzed.
`summary`	No	engagement dimension: aggregate statistics over the sampled posts (reposts of other authors excluded).
`topPosts`	No	engagement dimension: up to 10 posts ranked by total engagement.
`network`	No	network dimension: headline follow-graph counts for the account.
`analysis`	No	Dimension-specific analysis: graph classification for 'network', post-performance statistics for 'strategy'.
`insights`	No	Dimension-specific insights: structured content patterns for 'engagement', human-readable strings for 'network'.
`recommendations`	No	Dimension-specific recommendations: actionable strings for 'engagement', a structured plan for 'strategy'.

Tool Definition Quality

A4.6/5.0

Behavior5/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true. The description adds useful context: requires authentication, is read-only, and subject to per-tool rate limiting. 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?

The description is three sentences, each adding distinct value: core function, authentication/read-only, and usage alternatives. 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 tool has 10 parameters and an output schema, the description covers key aspects (purpose, auth, mutation, rate limiting, sibling differentiation) without being exhaustive. It's sufficient for most agents.

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 the description does not need to explain parameters. The description adds minimal extra value beyond the schema (e.g., default behavior for 'actor'). Baseline of 3 is appropriate.

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 'analyze', the resource 'a single account', and the constraint 'along one dimension'. It also distinguishes from the sibling tool 'find_influential_users' by noting the alternative use case.

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

Usage Guidelines5/5

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

The description explicitly says 'One account-analysis tool: pick a dimension' and directs users to 'find_influential_users' for topic/search-based discovery. It also mentions authentication requirement, providing clear when-to-use and when-not-to-use guidance.

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

Lightport: Open-Sourcing Glama's AI Gateway
By punkpeye on April 27, 2026.
open source
OpenAI
Tool Definition Quality Score (TDQS)
By punkpeye on April 3, 2026.
mcp
The Hackers Who Tracked My Sleep Cycle
By punkpeye on March 26, 2026.
security

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

URL: https://glama.ai/mcp/servers/cameronrye/atproto-mcp/tools/analyze_account

⇱ analyze_account - AT Protocol MCP Server | Glama