Skip to main content
Glama

Profile statistics

profile_stats
Read-only

Profile counters of a connected Instagram, Threads, Mastodon or Bluesky account. Threads returns a current followers snapshot; following and post count are unavailable and remain null. Cached values may be returned. A numeric zero is valid; null and unavailable explain absent data, missing permission or pending approval. PERMISSION_REQUIRED means analytics permission is missing. When new analytics consent is enabled for this user, ask them to reconnect the same channel in Publora Channels (/dashboard/accounts) in the same environment and grant analytics permission; retry after reconnect. If new consent is disabled, an operator must enable it first; reconnect alone cannot add the permission. AUTH_REVOKED also requires reconnect. APP_REVIEW_PENDING means the feature is disabled or awaiting approval; reconnect does not fix it. Requires personal analytics access and the backend's platform availability checks; Company accounts are unsupported.

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": {
      "platform": "<platform>",
      "platformId": "<platformId>"
    },
    "name": "profile_stats"
  }
}

Input Schema

NameRequiredDescriptionDefault
platformYesPlatform of the account
platformIdYesConnection ID from list_connections (prefix optional)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / platform / enum
      Previous value: -[
      -  "instagram",
      -  "mastodon",
      -  "bluesky"
      -]New value: +[
      +  "instagram",
      +  "threads",
      +  "mastodon",
      +  "bluesky"
      +]
  2. Changed1 schema field changed
    • changedInput schema / properties / platform / enum
      Previous value: -[
      -  "mastodon",
      -  "bluesky"
      -]New value: +[
      +  "instagram",
      +  "mastodon",
      +  "bluesky"
      +]
  3. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the readOnly/openWorld annotations, it discloses that values may be cached, that Threads returns only a followers snapshot with following/post counts null, that numeric zero is a legitimate value distinct from null, and what each error code means operationally. It maps each error to a remediation path and explicitly says reconnect does not fix APP_REVIEW_PENDING — exactly the behavioral context an agent needs.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is front-loaded with the core purpose, then null semantics, then error handling — a logical progression with no filler. The consent/reconnect section is dense and long, but each clause maps to a distinct remediation branch, so little is truly removable.

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?

With no output schema, the description must carry the return-value burden, and it does explain null/zero semantics and the Threads snapshot, plus full error taxonomy and account-type constraints. It stops short of naming the concrete fields returned for Instagram, Mastodon and Bluesky, leaving the exact payload shape partially implicit.

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% and the platformId description already points at list_connections, so the schema carries parameter meaning on its own. The description adds platform-dependent output behavior tied to the 'platform' enum (Threads limitations), which is useful context but is about results rather than parameter values, so the baseline 3 stands.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the concrete resource ('profile counters') and enumerates the four supported platforms, so an agent knows immediately this returns follower/following/post counts rather than post-level metrics. It does not explicitly contrast itself with the sibling post_stats, so the distinction between profile-level and post-level stats is left to inference from names.

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?

It clearly states prerequisites: personal analytics access is required, Company accounts are unsupported, and backend platform availability checks apply. It also prescribes the correct follow-up action per failure mode (reconnect for PERMISSION_REQUIRED/AUTH_REVOKED, operator enablement when new consent is disabled, nothing helps for APP_REVIEW_PENDING). What is missing is an explicit statement of when to prefer this over post_stats.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.