Skip to main content
Glama
Sign In

Mondovo

by com.mondovo.app
OverviewDiscussionsAdmin

How published posts did

get_post_performance
Idempotent

Numbers for posts that already went out — views, reach, likes, comments, shares, saves and so on, per account, with when they were read. Pass post_id for one post, or from/to (YYYY-MM-DD, inclusive, by when they went out; default the last 7 days, at most 92) for the brand's posts in that range. Numbers older than an hour are re-read. A metric a platform does not report is left out, never shown as 0. X numbers cost money to read, so they are re-read only for ONE post with include_x: true when the user asks about it; LinkedIn personal profiles cannot be read and say so. Free (no Creative Credits).

Input Schema

NameRequiredDescriptionDefault
toNoLast day, YYYY-MM-DD. Ignored with post_id.
fromNoFirst day, YYYY-MM-DD. Ignored with post_id.
post_idNoThe post id from get_calendar
brand_idYesBrand workspace id from list_brands
include_xNoAlso re-read X numbers for this ONE post. Only with post_id, and only when the user asked about this post.
user_goalNoOptional: the user's goal behind this call, in one short sentence of plain words (e.g. "add a page so customers can book tables"). No names, emails or other personal details.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / user_goal
      Added value: +{
+  "description": "Optional: the user's goal behind this call, in one short sentence of plain words (e.g. \"add a page so customers can book tables\"). No names, emails or other personal details.",
+  "type": "string"
+}
  2. Added

TDQS

A4.6/5.0
Behavior5/5

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

The description adds substantial behavior beyond the annotations: freshness rules, missing metrics being omitted rather than zeroed, X metric cost and re-read restrictions, and LinkedIn personal-profile limitations. It also clarifies that the call is free in terms of Creative Credits despite the X-specific cost behavior.

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?

The description is front-loaded with the core purpose and metrics, then moves into selection rules and limitations. It is dense but appropriate for a multi-parameter analytics tool, with little obvious filler.

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 complex analytics tool with no output schema, the description covers the key call modes, defaults, freshness behavior, platform limitations, and cost caveats. An agent has enough information to call it correctly without needing additional prose.

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 schema already documents all parameters. The description still adds useful semantics: post_id versus date-range selection, inclusive YYYY-MM-DD dates, last-7-days default, 92-day maximum, and the one-post-only restriction on include_x.

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 states a specific resource and scope: performance numbers for posts that already went out, including named metrics and per-account grouping. It distinguishes this from adjacent tools such as get_calendar and refresh_x_post_performance by focusing on reading post performance rather than scheduling or refreshing X data.

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 explains the two usage modes: post_id for one post, or from/to for the brand's posts in a date range. It also gives an explicit when-not constraint for include_x and notes LinkedIn personal profiles cannot be read, though it does not name alternative sibling tools.

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

All Mondovo toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources