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

prompteye-mcp

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

List the public reports of the account

list_reports
Read-only

Fetch generated visibility reports newest first to review agency leads, including scores, contact requests, and conversion status; sort by contact count to find interested prospects.

Instructions

Every report this key's account has generated, newest first — the agency's lead pipeline. A public report is PromptEye's lead magnet, sold to agencies white-label: a prospect fills in a form on the agency's site, PromptEye works out the industry, asks a set of assistants how visible that brand is, and emails back a page in the agency's branding — a visibility score, the competitors ahead of them, and quotes from what the assistants actually said. It is a one-off sample, not tracking: nothing is measured again until the report is converted into a project, which happens in the PromptEye app. leadStatus and the conversion are the agency's sales pipeline, and contactCount is how many times the brand asked to be contacted from the page.

Each row carries the visibility score, whether the prospect asked to be contacted, and whether the report has been converted into a tracked project. Sorting the work by contactCount is how the interested leads are found.

Input Schema

NameRequiredDescriptionDefault
limitNoHow many entries to return, at most 200. Defaults to 50.
cursorNoThe nextCursor of the previous page. Omit it to start from the first one.

Output Schema

NameRequiredDescriptionDefault
dataYes
nextCursorYesPass as cursor to read the next page. null = this was the last page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.0.22
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": false,
+  "properties": {
+    "data": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "brand": {
+            "type": "string"
+          },
+          "contactCount": {
+            "description": "How many times the brand asked to be contacted from the report page.",
+            "type": "number"
+          },
+          "country": {
+            "description": "Market the report was taken in, ISO 3166-1 alpha-2.",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "createdAt": {
+            "description": "When the report was ordered, ISO 8601 in UTC.",
+            "type": "string"
+          },
+          "domain": {
+            "description": "Website without `www.`. null = the form carried no website.",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "email": {
+            "type": "string"
+          },
+          "id": {
+            "type": "string"
+          },
+          "language": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "leadStatus": {
+            "description": "new, in_progress or done; moved in the PromptEye app, not through the API.",
+            "type": "string"
+          },
+          "projectId": {
+            "description": "The project the report was converted into. null = still only a sample.",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "reach": {
+            "description": "How far the brand sells: local, regional or national.",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "readyAt": {
+            "description": "When it finished, ISO 8601 in UTC. null = not finished yet.",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "score": {
+            "description": "Visibility of the brand in whole percent 0-100. null = the report is not ready yet.",
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "status": {
+            "description": "processing until the assistants have answered, then ready, or error.",
+            "type": "string"
+          },
+          "url": {
+            "type": "string"
+          },
+          "utm": {
+            "type": [
+              "string",
+              "null"
+            ]
+          }
+        },
+        "required": [
+          "id",
+          "brand",
+          "domain",
+          "email",
+          "status",
+          "score",
+          "reach",
+          "country",
+          "language",
+          "utm",
+          "leadStatus",
+          "projectId",
+          "contactCount",
+          "createdAt",
+          "readyAt",
+          "url"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "nextCursor": {
+      "description": "Pass as cursor to read the next page. null = this was the last page.",
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "required": [
+    "data",
+    "nextCursor"
+  ],
+  "type": "object"
+}
  2. Addedv1.0.16

TDQS

A3.9/5.0
Behavior5/5

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

Annotations already declare read-only and open-world behavior, but the description adds substantial domain context: reports are public lead magnets, one-off samples that are not tracked, conversion happens in the PromptEye app, and each row carries visibility score, contact status, and conversion state. This exceeds what the structured fields convey.

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

Conciseness3/5

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

The description is front-loaded with the core list operation, but it runs long and includes narrative product background about how PromptEye generates reports. That detail is useful for domain context but goes beyond what is needed to invoke a simple list tool.

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?

Given the existence of an output schema, annotations, and complete input-schema descriptions, the description provides more than enough context to understand the resource and its business meaning. It covers the report lifecycle and relevance of returned fields without needing to explain pagination mechanics already documented in the schema.

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 description coverage is 100%, so limit and cursor are fully documented in the input schema. The description adds no additional parameter meaning beyond what the schema provides, making the baseline 3 appropriate.

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 sentence states a specific resource and scope: 'Every report this key's account has generated, newest first.' It also distinguishes public reports from tracked projects, but it does not explicitly name or contrast sibling tools like get_report or create_report.

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?

The description gives a practical use case ('Sorting the work by contactCount is how the interested leads are found') and frames reports as the agency lead pipeline. However, it does not state when to use this tool instead of alternatives such as get_report or create_report.

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