Skip to main content
Glama

Visibility Genies

Read a saved perception analysis

get_saved_perception
Read-only

Reads a perception analysis saved on the Perception page: how the AI answers the project already bought (Prompt Explorer answers, or one tracked prompt's runs) describe a brand and its competitors. Each brand's sentiment with a score from -100 to 100 and the answers behind it, the themes behind that with a quote found in one answer and the cited sites that drive each theme, and for a tracked prompt each brand's score run by run. Also lists every saved analysis. Uses no credits and calls no provider. No agent tool runs an analysis: it runs on the page, which prices it first.

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_saved_perception"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectIdYesRequired. The Visibility Genies project this call works in and is billed to. Call list_projects to find one.
analysisIdNoThe saved analysis to read, from this tool's list. Omit to read the newest.

Output Schema

NameRequiredDescriptionDefault
metaNo
brandsYes
themesYes
analysesYes
analysisYes
overTimeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover read-only and closed-world, but the description adds genuinely new behavior: it consumes no credits, calls no provider, and no agent tool can trigger an analysis (it runs on the page and is priced there first). It also describes the shape of returned content (sentiment -100 to 100, themes with quotes, cited sites, per-run scores).

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 with the core action, and the credit/provider and page-only caveats come last where they belong. The first sentence is dense with nested parentheses and could be split, but no sentence is filler.

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 values need not be explained, yet the description still outlines the analysis contents and the enumeration capability, which is helpful. It lacks only explicit sibling routing for an agent choosing among many saved-read tools.

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 both parameters are documented structurally, but the description adds a source for analysisId: the tool itself lists every saved analysis, making the ID discoverable here. It does not restate the omit-for-newest default, which the schema already carries.

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?

Opens with a concrete verb and resource ('Reads a perception analysis saved on the Perception page') and scopes it to Prompt Explorer answers or a tracked prompt's runs. It also states the negative case that no agent tool runs an analysis, which separates it from analysis-producing siblings, though it never names the overlapping read siblings such as get_saved_prompt_answers or get_saved_brand_mentions.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied rather than stated: the agent learns this is how to fetch an already-saved perception analysis and that it can enumerate saved ones. There is no explicit when-to-use/when-not versus the many other get_saved_* read tools, so selection still requires the agent to infer from names.

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