Skip to main content
Glama

get_format_performance

Read-only

Answer "what type of post works best?", "do images or videos perform better?", "which format gets the most engagement?" for a platform. Ranks post formats (text, image, video, etc.) by engagement. On LinkedIn it is each format's median engagement rate per post, with how many posts it is based on, so a format with only a post or two can be read with care; it covers member profiles' posts only, not company pages. With too few posts it says there isn't enough data yet. WHOSE POSTS: pass author whenever the question names one. "my"/"I" -> author: "me". A person's name -> that name, e.g. author: "Alex". "our"/"the team", or no one named -> omit author for the whole workspace. For overall numbers use get_analytics_summary; for single posts, list_top_posts.

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>"
    },
    "name": "get_format_performance"
  }
}

Input Schema

NameRequiredDescriptionDefault
authorNoWhose posts to compare. "me" for the person asking, or a teammate's name for theirs ("Alex"). Omit for the whole workspace, which is the default and is what "our" / "the team" means.
periodNoRolling window ending today. Default 30d. For any other window, pass start_date/end_date instead.
end_dateNoOptional. Last day of a custom range, YYYY-MM-DD, inclusive. Defaults to today. Needs start_date.
platformYesRequired. The network to analyze.
workspaceNoOptional: the workspace (client) to answer from for this call only, by name (e.g. 'Acme') or numeric id, as returned by list_workspaces. Leave it out to use the current workspace. It does not change the current workspace; use select_workspace for that.
start_dateNoOptional. First day of a custom range, YYYY-MM-DD, in the user's timezone. Use for windows the presets don't cover: "last 14 days", "in March", "since Jan 1", "last year". Overrides `period`. Ranges can cover up to 366 days.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / author
      Added value: +{
      +  "description": "Whose posts to compare. \"me\" for the person asking, or a teammate's name for theirs (\"Alex\"). Omit for the whole workspace, which is the default and is what \"our\" / \"the team\" means.",
      +  "type": "string"
      +}
  2. Changed1 schema field changed
    • addedInput schema / properties / workspace
      Added value: +{
      +  "description": "Optional: the workspace (client) to answer from for this call only, by name (e.g. 'Acme') or numeric id, as returned by list_workspaces. Leave it out to use the current workspace. It does not change the current workspace; use select_workspace for that.",
      +  "type": "string"
      +}
  3. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations only declare it is a safe read, so the description carries the real behavioral burden and does so: on LinkedIn the metric is median engagement rate per post plus the post count, member profiles only (not company pages), and low-volume cases return an explicit 'not enough data yet' signal. This tells the agent both how to interpret results and when results are unreliable, which annotations cannot convey.

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?

Front-loaded with the user questions it serves, then the ranking behavior, then a clearly labeled 'WHOSE POSTS:' block for parameter routing, then sibling alternatives. No filler sentences, and the platform-specific caveat is placed where it will be read before invocation.

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?

There is no output schema, and the description compensates by describing the result shape (formats ranked with per-format median rate and post counts), the LinkedIn caveat, and the insufficient-data case. For a read-only analytics tool with six fully documented parameters, nothing material is missing.

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 parameters like `period`, `start_date`/`end_date` precedence, and `workspace` are already fully documented. The description restates the `author` semantics ('me', a name, omit for workspace) which the schema already covers, though the interpretive mapping from question phrasing adds modest routing value. Baseline 3 is appropriate when the schema does the heavy lifting.

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 and resource: it ranks post formats (text, image, video) by engagement for a given platform, and it front-loads the three natural-language questions it answers. An agent can immediately distinguish this from the sibling analytics tools.

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?

Explicitly routes away: 'For overall numbers use get_analytics_summary; for single posts, list_top_posts.' It also gives a concrete decision rule for the `author` parameter, mapping 'my'/'I' to 'me', a person's name to that name, and 'our'/'the team' or an unnamed subject to omitting `author`.

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