Skip to main content
Glama

Get how each prompt performs

get_prompt_performance
Read-onlyIdempotent

Per tracked prompt: how often AI names the member's brand, how often it's recommended, the leading tracked competitor, which brands AI names instead in the answers that leave the member out (including brands they don't track yet), and change vs the previous period. Sorted to show the prompts you're losing first. Use for "which questions don't mention us?", "who wins the questions we're missing?" or "where is a competitor leading?". Needs sign-in to Kliqo (read-only).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_prompt_performance"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
rangeNo30d
projectNoProject name, domain or id; leave out for the workspace's current project

Output Schema

NameRequiredDescriptionDefault
statusYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and non-destructive behavior, so the safety bar is largely met. The description adds genuinely useful context beyond that: the result is sorted to surface losing prompts first, the 'brands named instead' set includes brands the member does not track yet, and calls require Kliqo sign-in. It does not cover pagination or how 'previous period' is derived.

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 metric list is front-loaded in the first sentence, followed by sorting behavior, then use cases, then the auth prerequisite — a sensible ordering. It is dense but every clause carries information; the only near-redundancy is restating 'read-only' which annotations already declare.

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?

An output schema exists so return-value shape need not be explained, and annotations cover the safety profile; the description fills in purpose, sort order, audience-inclusion semantics and auth. The remaining gap is the unparameterized `limit` and `range`, which an agent must infer from the schema alone.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 33% — only `project` is documented, while `limit` and `range` carry no schema descriptions. The description does not mention any parameter, not even the 1-40 limit or the 7d/30d/90d range; 'change vs the previous period' only loosely hints at the range parameter. With low coverage, the description should compensate and does not.

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 names a specific verb+resource (per tracked prompt performance) and enumerates the exact metrics returned: brand naming frequency, recommendation rate, leading competitor, brands named in place of the member, and period-over-period change. An agent can distinguish this from siblings like get_competitor_gaps or get_ai_visibility because the output is explicitly prompt-level and loss-sorted.

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?

Three concrete trigger questions ('which questions don't mention us?', 'who wins the questions we're missing?', 'where is a competitor leading?') give clear usage context. It stops short of naming an alternative sibling to use instead when the agent wants aggregate-level rather than prompt-level data, so no explicit exclusions.

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