Skip to main content
Glama

Visibility Genies

Read tracked prompts

get_tracked_prompts
Read-only

Reads Prompt Tracking in this project: the prompts asked again on a schedule, the brand each watches for, and, for one tracked prompt, every run with how many of each model's or app's answers over a period name the brand (the visibility rate, with the number of answers), each answer's rank for the brand in the list that names it ('2nd of 5 in its list', items counted whatever they name), which varies from run to run, and the sites the answers cite most, the project's own marked. Uses no credits and calls no provider. No agent tool sets up, runs or changes a tracked prompt: the Prompt Tracking page prices each schedule and the person approves it there.

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": {
      "projectId": "<projectId>"
    },
    "name": "get_tracked_prompts"
  }
}

Input Schema

NameRequiredDescriptionDefault
periodNoThe runs the share of answers naming the brand is counted over. Defaults to the last 90 days.
projectIdYesRequired. The Visibility Genies project this call works in and is billed to. Call list_projects to find one.
trackedPromptIdNoThe tracked prompt to read run by run, from this tool's list. Omit to list every tracked prompt.

Output Schema

NameRequiredDescriptionDefault
metaNo
trackedPromptYes
trackedPromptsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already establish readOnlyHint=true, openWorldHint=false and destructiveHint=false, so safety is covered. The description adds genuinely new operational facts beyond them: 'Uses no credits and calls no provider' tells the agent this is free and offline, and the closing sentence states no agent tool can mutate tracked prompts. It does not discuss volume, latency, or pagination for the per-run expansion.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The body is essentially one enormous sentence with nested parentheticals ('the visibility rate, with the number of answers', 'items counted whatever they name', 'which varies from run to run') that is hard to parse on a first read. Much of its length re-describes return values that the output schema already specifies, so the bulk is redundant rather than load-bearing. Only the first clause and the last sentence carry unique value.

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?

With an output schema present, the description needn't define return values, yet it still covers cost ('no credits'), side-effect absence (no setup/run/change via agent), and the period default. Combined with full schema coverage and annotations, an agent has enough to call it correctly. The only gap is that per-run expansion volume is unmentioned.

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% and all three parameters carry their own descriptions, including the default for period and the 'omit to list' behaviour for trackedPromptId. The description restates the same period scoping ('over a period name the brand') without adding syntax or constraint detail beyond the schema. Baseline 3 applies where the schema does the heavy lifting.

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 opening clause 'Reads Prompt Tracking in this project' gives a specific verb and a distinct resource, and the follow-on enumerates what it returns: scheduled prompts, the watched brand, per-run visibility rates, answer ranks, and cited sites. No sibling covers tracked prompts, so it is separable from the surrounding get_/read_ tools by resource alone. It stops short of 5 because the purpose is buried inside one long run-on clause, and no sibling is named for contrast.

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?

The final sentence gives an explicit exclusion: 'No agent tool sets up, runs or changes a tracked prompt', redirecting the agent to the Prompt Tracking page where a person approves and prices the schedule. It also implies the read/list split via 'Omit to list every tracked prompt'. There is no named alternative tool for adjacent questions, so usage is clear but not fully routed.

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