Skip to main content
Glama
Sign In

StealAds

by ai.stealads
OverviewDiscussionsAdmin

Update a collection

update_collection
Idempotent

Renames one of the user's collections or changes its description; at least one of the two is needed. The saved ads inside it are not affected.

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": {
      "collection_id": "<collection_id>"
    },
    "name": "update_collection"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoNew collection name, up to 200 characters.
descriptionNoNew description, up to 2,000 characters; null clears it.
collection_idYesCollection id from list_collections.

Output Schema

NameRequiredDescriptionDefault
collectionNoThe private saved-ad collection.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / collection_id / description
      Previous value: -"Collection reference from list_collections; null selects unsorted saved ads where supported."New value: +"Collection id from list_collections."
    • changedInput schema / properties / description / description
      Previous value: -"Short description of this item."New value: +"New description, up to 2,000 characters; null clears it."
    • changedInput schema / properties / name / description
      Previous value: -"Name of this brand or collection."New value: +"New collection name, up to 200 characters."
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and idempotentHint=true, so the safety profile is known. The description adds two pieces of non-obvious behavior: that at least one of name/description must be supplied, and that saved ads inside the collection are unaffected by the update — a meaningful side-effect disclosure that 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?

One tightly written sentence with the operation front-loaded and the two secondary facts (mutual requirement, no effect on saved ads) appended. Nothing is redundant against the title or 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?

An output schema exists, so return values need no explanation, and annotations cover the mutation/idempotency profile. Combined with the description's coverage of the field constraint and the non-effect on contained ads, an agent has everything needed to call this correctly.

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 field-level meaning is already documented (including that null clears the description). The description still adds a cross-parameter constraint the schema does not express — the schema only lists collection_id as required, yet the description states that at least one of the two editable fields is needed — which is genuinely additive.

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 description names concrete operations (rename, change description) on a specific resource (one of the user's collections), so an agent knows exactly what the tool mutates. It does not explicitly contrast itself with create_collection or delete-type siblings, but the resource-plus-operation pairing is unambiguous.

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?

Usage context is implied by 'renames... or changes its description; at least one of the two is needed', which tells the agent the minimum viable invocation but not when to prefer this over, say, create_collection. No explicit exclusions or prerequisites (e.g. ownership/permission requirements) are stated.

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

All StealAds toolsInspect
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