Mark

Rename Competitor

rename_competitor

Idempotent

Changes a competitor's name, tracked or not, like the rename on its profile. AI answer matching uses the new name for past and future weekly answers. Trims the name and refuses a blank one or one over 100 characters. Related: list_competitors, track_competitor, set_competitor_aliases.

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": {
      "competitorId": "<competitorId>",
      "name": "<name>"
    },
    "name": "rename_competitor"
  }
}

Input Schema

Name	Required	Description	Default
`name`	Yes	The new name, as AI answers would write it.
`competitorId`	Yes	Competitor id from list_competitors.

Output Schema

Name	Required	Description	Default
`competitor`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 23, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Goes well beyond annotations by disclosing a non-obvious side effect: AI answer matching applies the new name to past and future weekly answers, i.e., retroactive relabeling. It also states the input normalization (trimming) and validation rejections (blank, >100 chars), which annotations cannot convey.

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?

Three short sentences with the mutation, its downstream effect, and its validation rules front-loaded, plus a single related-tools line. No filler and no redundancy with the schema.

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?

Output schema exists so return details needn't be described; with side effects and validation rules covered, an agent has everything required to call this correctly on tracked or untracked competitors.

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 covers both parameters at 100%, so baseline is 3; the description adds real value with constraints the schema lacks (trim behavior, refusal of blank names and names over 100 characters). Schema description still guides the ID source (list_competitors), so no more than a 4 is warranted.

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 and resource ("Changes a competitor's name") plus scope ("tracked or not"), and the third sentence implies the distinction from set_competitor_aliases by delivering a full rename with downstream matching effects. An agent can distinguish it from sibling naming/alias tools without opening the schema.

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?

Clarifies that the tool works on tracked and untracked competitors, which matters given the presence of track_competitor/untrack_competitor siblings, and points to related tools (list_competitors for IDs, set_competitor_aliases for alternatives). It stops short of an explicit when-not/exclusion clause.

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

All Mark 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.

Resources

Need Help?