mcp-server

set_marketplace_name

DestructiveIdempotent

MARKETPLACE name — set or clear the human-readable name of a marketplace so you (and the user) can identify it later. Names are free-text and NOT unique — use this to give an unnamed marketplace a memorable label, or to rename one. Pass name:"" (empty) to clear the name back to none. Returns {integrationId, action:'set_name', status:'updated', kind, editUrl, message}. marketplace_id is from list_marketplaces. project_id is OPTIONAL (inferred for a single-project customer; project_id_required otherwise — then call list_projects).

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": {
      "marketplace_id": "<marketplace_id>",
      "name": "<name>"
    },
    "name": "set_marketplace_name"
  }
}

Input Schema

Name	Required	Description
`name`	Yes	New name; pass an empty string to clear the name.
`project_id`	No
`marketplace_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 1, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Adds real context beyond the annotations: names are free-text and non-unique, empty string resets to none, and the return payload is enumerated. The annotations declare destructiveHint=true, and the description does not explain why a rename is flagged destructive or what else could be affected — the one remaining gap.

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

Conciseness4/5

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

Front-loads the effect, then clearing behavior, return shape, and prerequisites in a logical order with no wasted sentences. The capitalization emphasis (MARKETPLACE, NOT, OPTIONAL) is slightly noisy but aids scanning rather than bloating the text.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a three-parameter mutation with no output schema, the description supplies the return fields, ID sourcing, and clearing semantics. The only missing piece is any note on the destructive flag or whether a prior name can be recovered, which matters for a mutation tool.

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 33%, so the description must carry the load and it does: name semantics including the empty-string clear, marketplace_id provenance (list_marketplaces), and project_id being optional with an inference rule and list_projects fallback. That covers all three parameters with meaning not present in the schema.

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 — set or clear the human-readable name of a marketplace — and names the sibling it must be distinguished from implicitly by the 'marketplace vs ad' qualifier. An agent can pick it apart from set_ad_name and set_feed_name 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?

Gives clear when-to-use cases (label an unnamed marketplace, rename an existing one) and the clearing case, plus the prerequisite routing: marketplace_id from list_marketplaces, and list_projects when project_id_required is raised. It lacks an explicit 'do not use this for X' exclusion, but the retrieval paths for IDs are spelled out.

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

All mcp-server 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?