Skip to main content
Glama
Sign In

StealAds

by ai.stealads
OverviewDiscussionsAdmin

Unsave an ad

unsave_ad
DestructiveIdempotent

Removes an ad from the user's saved ads and returns deleted: true; an ad that was not saved returns deleted: false. The ad itself is not deleted and can be saved again with save_ad.

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>"
    },
    "name": "unsave_ad"
  }
}

Input Schema

NameRequiredDescriptionDefault
ad_idYesAd id of a saved ad, from list_saved_ads.

Output Schema

NameRequiredDescriptionDefault
deletedNodeleted value in this response.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field 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."
  2. First observed

TDQS

A4.5/5.0
Behavior5/5

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

The description adds important behavior beyond annotations: it explains that deleted: true means unsaved, deleted: false means it was not saved, and the ad itself is not deleted. This clarifies the scope of destructiveHint=true without contradicting it, because the destructive effect is limited to removing the saved relationship.

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?

The description is two short sentences, front-loads the action, and every detail earns its place by clarifying the return semantics and the non-permanent nature of the operation.

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?

For a one-parameter mutation with annotations and an output schema, the description provides the key missing context: the meaning of deleted true/false, that the ad remains available, and that save_ad can reverse the action.

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 coverage is 100%, so the ad_id parameter is already fully documented in the schema, including that it comes from list_saved_ads. The description only implies that the input is a saved ad and does not add syntax or format details beyond 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?

The description states a specific verb and resource: it removes an ad from the user's saved ads. It also distinguishes the action from permanent deletion and from save_ad, so an agent can tell exactly what this tool does.

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?

Usage is clear from context: use this tool to unsave an ad, and use save_ad if the ad should be saved again. However, it does not explicitly discuss alternatives such as move_saved_ad or when unsaving should be preferred over other saved-ad operations.

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