prompteye-mcp

Official

Overview Schema Source Related Servers Discussions Admin

Update project settings

update_project

Correct what the project tracks: change the display name, grouping label, primary domain, alternative brand spellings, and alternative domains.

Instructions

Correct what the project tracks: change the display name, grouping label, primary domain, alternative brand spellings, and alternative domains.

Note: alternativeBrandNames and alternativeDomains are replaced as a whole rather than appended to, so pass the complete list. Neither the brand name nor the market country can be changed here because historical measurements depend on them (a different brand/market is a separate project).

Before changing alternativeBrandNames, warn the user that historical visibility metrics will be rebuilt. The rebuild may take up to an hour. During that time, aggregated reads such as list_competitors and list_prompt_groups may be temporarily unavailable.

Brands kept out of competitor rankings are not part of the project payload; read them with list_competitor_exclusions and change them with set_competitor_exclusions.

Input Schema

Name	Required	Description
`name`	No	Display name of the project. Defaults to the brand name.
`label`	No	Short label used to group projects in listings.
`domain`	No	Primary domain of the brand, without protocol or path, e.g. prompteye.com.
`projectId`	Yes	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.
`alternativeDomains`	No	Further domains owned by the brand whose citations count as its own. Replaces the existing list.
`alternativeBrandNames`	No	Other spellings that count as naming the brand. Replaces the existing list and triggers a rebuild of historical visibility metrics that may take up to an hour; warn the user that aggregate reads may be temporarily unavailable during the rebuild.

Output Schema

Name	Required	Description
`id`	Yes
`name`	Yes
`brand`	Yes
`label`	Yes	Grouping label. null = the project has none.
`domain`	Yes
`country`	Yes
`createdAt`	Yes	When the project was created, ISO 8601 in UTC.
`publicUrl`	No	Link anyone can open without logging in to view the project. null = the project is not shared.
`accessRole`	Yes	OWNER manages the project, FULL_ACCESS edits it, READ_ONLY reads it.
`alternativeDomains`	Yes
`alternativeBrandNames`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv1.0.28Oct 23, 2026

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

addedInput schema / required
```
Added value: +[
+  "projectId"
+]
```

addedOutput schema / properties / publicUrl

Added value: +{
+  "description": "Link anyone can open without logging in to view the project. null = the project is not shared.",
+  "type": [
+    "string",
+    "null"
+  ]
+}

Changed1 schema field changedv1.0.22Oct 2, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": false,
+  "properties": {
+    "accessRole": {
+      "description": "OWNER manages the project, FULL_ACCESS edits it, READ_ONLY reads it.",
+      "type": "string"
+    },
+    "alternativeBrandNames": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "alternativeDomains": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "brand": {
+      "type": "string"
+    },
+    "country": {
+      "type": "string"
+    },
+    "createdAt": {
+      "description": "When the project was created, ISO 8601 in UTC.",
+      "type": "string"
+    },
+    "domain": {
+      "type": "string"
+    },
+    "id": {
+      "type": "string"
+    },
+    "label": {
+      "description": "Grouping label. null = the project has none.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "name": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "id",
+    "name",
+    "brand",
+    "domain",
+    "country",
+    "label",
+    "alternativeBrandNames",
+    "alternativeDomains",
+    "accessRole",
+    "createdAt"
+  ],
+  "type": "object"
+}

Changed1 schema field changedv1.0.18Sep 24, 2026

changedInput schema / properties / alternativeBrandNames / description

Previous value: -"Other spellings that count as naming the brand. Replaces the existing list."New value: +"Other spellings that count as naming the brand. Replaces the existing list and triggers a rebuild of historical visibility metrics that may take up to an hour; warn the user that aggregate reads may be temporarily unavailable during the rebuild."

Addedv1.0.12Sep 20, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Goes well beyond the annotations (readOnlyHint=false, destructiveHint=false, idempotentHint=false) by disclosing that alternative lists are replaced wholesale rather than appended, that changing alternativeBrandNames triggers a historical-metrics rebuild of up to an hour, and that aggregated reads like list_competitors and list_prompt_groups may be temporarily unavailable. These are exactly the side effects an agent needs before writing.

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?

Front-loaded with what is editable, then constraints, then side effects, then routing to the sibling tool for exclusions. Three short paragraphs, each sentence carrying distinct operational value.

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?

An output schema exists so return values need no explanation; with six params and 100% schema coverage, the description closes the remaining gaps (replace semantics, rebuild side effects, out-of-scope fields, sibling routing). Nothing needed to call it correctly is missing.

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 the baseline is 3; the description still adds value by warning that replacement (not append) semantics apply to both alternative lists and by naming fields that deliberately have no parameter (brand name, market country). It does not restate field formats, which is fine since the schema covers them.

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?

States a specific verb+resource ("Correct what the project tracks") and enumerates the exact editable fields: display name, grouping label, primary domain, alternative brand spellings, alternative domains. An agent can distinguish it from create_project or set_competitor_exclusions without opening any schema.

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?

Explicitly bounds scope: brand name and market country cannot be changed here because a different brand/market is a separate project, and competitor exclusions must be handled via list_competitor_exclusions / set_competitor_exclusions. It also prescribes a pre-call action (warn the user before changing alternativeBrandNames).

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

Deploy Server