Skip to main content
Glama
Sign In

StealAds

by ai.stealads
OverviewDiscussionsAdmin

Move a saved ad

move_saved_ad
Idempotent

Moves an ad that is already saved into one of the user's collections, or back to unsorted with collection_id null. save_ad saves an ad that is not saved yet. Repeating the same move changes nothing.

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

Input Schema

NameRequiredDescriptionDefault
ad_idYesAd id of a saved ad, from list_saved_ads.
collection_idYesTarget collection id from list_collections, or null for unsorted.

Output Schema

NameRequiredDescriptionDefault
savedAdNoThe saved-ad pointer and available evidence after this change.
operationNoWhether the saved-ad change inserted, updated or preserved the existing item.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / ad_id / description
      Previous value: -"Ad reference from search_ads, find_winning_ads or get_ad (e.g. the returned ad id)."New value: +"Ad id of a saved ad, from list_saved_ads."
    • changedInput schema / properties / collection_id / description
      Previous value: -"Collection reference from list_collections; null selects unsorted saved ads where supported."New value: +"Target collection id from list_collections, or null for unsorted."
  2. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare idempotentHint=true and destructiveHint=false, and 'repeating the same move changes nothing' largely restates idempotency rather than adding new context. Nothing is said about permission requirements or what happens if the ad is not actually saved, so the description adds only modest value beyond the structured fields.

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, front-loaded with the core action and destination semantics, with zero filler. The sibling disambiguation is placed immediately after the purpose statement.

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?

With an output schema, full parameter coverage, and rich annotations, the description covers nearly everything an agent needs to call it correctly. The only gap is error behavior when ad_id does not refer to a saved ad.

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

Parameters3/5

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

Schema description coverage is 100% and both parameters already document their sources (list_saved_ads, list_collections) and the null-for-unsorted convention. The description reinforces but does not extend the schema's parameter meaning.

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 (moves) and resource (an ad already saved) plus the two possible destinations, and explicitly contrasts with save_ad. An agent can distinguish it from save_ad and unsave_ad 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly routes unsaved ads to save_ad and explains that null collection_id means unsorted, giving clear conditions for use. It stops short of naming when NOT to use it (e.g., leaving a saved ad alone via unsave_ad), so guidance is strong but not exhaustive.

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