Mencoro

Update a project

update_project

DestructiveIdempotent

Rename a project, replace the website domains and brand names it is monitored for, or both. A rename alone removes nothing. brandProfile replaces both lists entirely: pass every domain and name the project should keep. A domain or brand name left out is removed, and later checks no longer match on it; results already recorded are not re-matched or deleted. Show the user the full new lists before calling. Safe to retry.

Input Schema

Name	Required	Description
`name`	No
`projectId`	Yes
`brandProfile`	No	Replaces the website domains and brand names the project is monitored for.
`organizationId`	Yes

Output Schema

Name	Required	Description	Default
`project`	Yes	The project after the rename; null when no name was given.
`brandProfile`	Yes	The brand profile after the replacement; null when no brandProfile was given.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 14, 2026
- changedInput schema / properties / brandProfile / type
```
Previous value: -[
-  "null",
-  "object"
-]New value: +[
+  "object",
+  "null"
+]
```
AddedSep 28, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Provides rich behavioral context beyond annotations: details exactly what gets removed by brandProfile replacement, clarifies that results already recorded are not re-matched or deleted, and confirms idempotency ('Safe to retry'). This exceeds the standard set by destructiveHint=true.

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?

Highly efficient: only 6 sentences, front-loads the core purpose and usage, then details the destructive semantics of brandProfile, ending with the safety precondition and idempotency note. No wasted words.

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?

Complete for a complex mutation tool. With an output schema present, return values needn't be explained. The description covers usage, destructive behavior, parameter semantics, and safety preconditions comprehensively.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 25%, so the description must compensate. It does so thoroughly: explains that brandProfile replaces lists entirely, warns that omitted items are removed, clarifies that a rename alone removes nothing, and specifies that brandProfile includes both domains and names.

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 specific verbs and resources ('Rename a project, replace the website domains and brand names it is monitored for, or both'), clearly distinguishing it from siblings like rename_cluster or update_competitor.

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?

Clearly states the two modes of operation and the critical precondition 'Show the user the full new lists before calling.' However, it doesn't explicitly differentiate when to use brandProfile vs name alone beyond the logical implied behavior.

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

All Mencoro tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.