Skip to main content
Glama
PROMPTEYE-SP-Z-O-O

prompteye-mcp

Official
by PROMPTEYE-SP-Z-O-O
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Read one brand analysis run

get_brand_analysis_run
Read-only

One run in full: its gaps, the ranking evidence behind each one, and the sentiment behind how the assistants talk about the brand.

Instructions

One run in full: its gaps, the ranking evidence behind each one, and the sentiment behind how the assistants talk about the brand. Call it after create_brand_analysis_run until status is ready — gaps is empty and sentiment is null until then, and error is set instead if it failed.

Input Schema

NameRequiredDescriptionDefault
runIdYesId of the run, as create_brand_analysis_run reports it.
projectIdYesThe project to work on — its id from list_projects. Required on every call, so that parallel conversations never read or write each other's project.

Output Schema

NameRequiredDescriptionDefault
idYes
gapsYesThe topics where a competitor answers better than this brand. Empty until ready.
errorYesWhy the run failed. null unless status is error or corrupted_response.
statusYesprocessing the moment it is requested, then ready, or error / corrupted_response when it failed — see error.
createdAtYesWhen the run was requested, ISO 8601 in UTC.
projectIdYes
sentimentYesHow the assistants talk about the brand when they mention it. null until ready.
totalCostYesPromptEye's internal AI processing cost in USD, not a charge to the user. null until the run finishes.
updatedAtYesWhen the run last changed, ISO 8601 in UTC.
maxContextGapsYesHow many gaps this run may report at most.
usedResultCountYesHow many tracking results fed this run.
activePromptCountYesHow many active tracked prompts fed this run.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.0.28
    • addedInput schema / properties / projectId
      Added value: +{
+  "description": "The project to work on — its id from list_projects. Required on every call, so that parallel conversations never read or write each other's project.",
+  "minLength": 1,
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "runId"
-]New value: +[
+  "projectId",
+  "runId"
+]
    • addedOutput schema / properties / totalCost / description
      Added value: +"PromptEye's internal AI processing cost in USD, not a charge to the user. null until the run finishes."
  2. Addedv1.0.22

TDQS

A4.7/5.0
Behavior5/5

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

Beyond readOnlyHint and openWorldHint, the description explains the asynchronous lifecycle: gaps and sentiment are unavailable until status is ready, and error appears on failure. This is exactly the behavioral context needed to poll correctly.

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?

It is two tightly written sentences: the first front-loads what the run contains, and the second provides the polling condition and failure state. No sentence is wasted.

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?

The tool is read-only, has a full input schema and an output schema, and the description covers the key non-schema behavior an agent needs: readiness, empty fields before ready, and error signaling. Nothing important 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?

The input schema has 100% coverage and already explains runId and projectId, including their source and required isolation behavior. The description adds no parameter-level detail beyond the schema, so the baseline of 3 is appropriate.

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 exactly what is returned: one run in full, including gaps, ranking evidence, and sentiment. It also distinguishes this read from create_brand_analysis_run by explicitly saying to call it after creation.

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?

It gives explicit timing guidance: call after create_brand_analysis_run, poll until status is ready, and expect gaps empty and sentiment null before readiness. It also clarifies that error is set if the run failed.

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

Deploy Server

Other Tools