Skip to main content
Glama

Page summary

get_page_summary
Read-onlyIdempotent

Followers, reach, impressions and profile views for one account over a window.

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": {
      "account_id": "<account_id>"
    },
    "name": "get_page_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNo
account_idYesThe social account id

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so safety is covered. The description adds the useful scoping detail that results cover one account over a time window, but says nothing about permissions, rate limits, data freshness, or how the window affects results.

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 a single efficient sentence that front-loads the metrics, with no wasted wording. The tradeoff is that terseness leaves the action and usage context implicit rather than explicit.

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

Completeness3/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 does help by enumerating the four returned metrics. However, it does not explain the structure of the response, the meaning of the time window, or when an agent should choose this over sibling analytics tools, leaving notable gaps for a summary endpoint.

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 description coverage is 50%: account_id is documented in the schema, while days has bounds and a default but no description. The phrase 'over a window' hints that days controls the reporting period, but it does not clarify the default of 28 days or whether the window is rolling or calendar-based.

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 specific metrics (followers, reach, impressions, profile views) and the scope (one account over a window), so the resource is clear. It stops short of an explicit retrieval verb and does not distinguish this from sibling analytics tools such as get_ads_overview or get_performance_digest.

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

Usage Guidelines2/5

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

There is no statement of when to use this tool versus the many sibling analytics tools, and no exclusions or prerequisites. The only implicit guidance is the word 'summary,' which is not enough to route an agent reliably.

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.

Resources