Skip to main content
Glama
AdaptlyPost

AdaptlyPost

Official

Get Platform Breakdown

get_platform_breakdown
Read-onlyIdempotent

Compare platform performance for a date range using per-platform followers, views, likes, comments, shares, posts, average views, and engagement rate to see which platform performs best.

Instructions

The overview metrics split per platform for a date window, for "which platform performs best" comparisons. Returns { platforms }: one row per platform with analytics data, carrying followers, views, likes, comments, shares, postsCount, avgViewsPerPost and engagementRate (each { value, previousValue, deltaPercent }) plus supportedMetrics, the metrics that platform actually reports; compare only metrics both platforms list there. Google Business Profile reports location impressions only. Takes no platform filter; connectionIds narrows it to some accounts. Use get_analytics_overview for the combined total.

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": {
      "from": "<from>",
      "to": "<to>"
    },
    "name": "get_platform_breakdown"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesEnd of the reporting window (ISO 8601). Must not be earlier than from
fromYesStart of the reporting window as an ISO 8601 date or instant (e.g. "2026-08-01"). Metrics cover posts published between from and to; the comparison window is the same length immediately before from
workspaceIdNoWorkspace to act in: an id from list_workspaces. Omit to act in the workspace list_workspaces marks current. Use the same workspaceId for every call about the same workspace, since ids from one workspace (accounts, posts, uploads) do not exist in another
connectionIdsNoRestrict to these accounts, by the account id from list_accounts; omit for every account

Output Schema

NameRequiredDescriptionDefault
resultYesAn object with platforms: one { platform, followers, views, likes, comments, shares, postsCount, avgViewsPerPost, engagementRate, supportedMetrics, accountActivityConnectionIds } per platform, where accountActivityConnectionIds lists the accounts counted by their account-wide daily activity instead of the posts published in the window.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.22.0

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world and non-destructive, so the safety profile is covered. The description still adds real behavior: the response shape (one row per platform), the supportedMetrics caveat, and the Google Business Profile quirk that only location impressions are reported. It stops short of mentioning rate limits or sync staleness (a sibling handles sync status), so a 4 rather than a 5.

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?

Front-loaded summary sentence followed by return-shape detail and then a sibling pointer — a sensible structure with no filler. Some of the metric-field enumeration is redundant when an output schema exists, but the enumeration is compact and earns partial credit by warning about non-uniform platform metrics.

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?

For a four-parameter read tool with full schema coverage and an output schema, this covers purpose, alternatives, data quirks and scoping. Nothing an agent needs in order to call it correctly is missing; the return-shape notes are surplus but harmless.

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 coverage is 100%, so the baseline is 3 and the schema carries date/workspace semantics. The description does add meaning beyond it: it tells the agent there is deliberately no platform filter and that connectionIds narrows rather than replaces the account scope, which prevents a wrong call attempt.

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?

States a specific verb-like operation (metrics split per platform) with scope (date window) and even names its intended question, "which platform performs best". It explicitly contrasts with the sibling get_analytics_overview, so the agent can differentiate without opening either schema.

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?

Gives when-to-use (platform comparison), when-to-use-otherwise (get_analytics_overview for combined totals), and a caveat about comparing only metrics both platforms report. It also clarifies a negative constraint — no platform filter, connectionIds narrows accounts — so exclusions are explicit.

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

Deploy Server

Other Tools