Skip to main content
Glama
Sign In

StealAds

by ai.stealads
OverviewDiscussionsAdmin

Create a collection

create_collection

Creates a private collection for sorting saved ads and returns it with its collection id. Each call creates a new collection, even when the name repeats. save_ad and move_saved_ad put ads into it.

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

Input Schema

NameRequiredDescriptionDefault
nameYesCollection name, up to 200 characters.
descriptionNoOptional note on what the collection is for, up to 2,000 characters.

Output Schema

NameRequiredDescriptionDefault
collectionNoThe private saved-ad collection.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / description / description
      Previous value: -"Short description of this item."New value: +"Optional note on what the collection is for, up to 2,000 characters."
    • changedInput schema / properties / name / description
      Previous value: -"Name of this brand or collection."New value: +"Collection name, up to 200 characters."
  2. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnly=false, destructive=false, idempotent=false and openWorld=false, so the safety profile is covered. The description adds concrete meaning to the non-idempotent hint by clarifying that repeated names produce separate collections rather than errors, and notes the collection is private. That is real added value but modest, so a 3 fits rather than a 4 or 5.

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 zero filler, front-loaded with the verb and resource, followed by the return behavior, the duplicate-name caveat, and the sibling handoff. Every sentence earns its place.

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?

Output schema exists, so the description needn't explain return values, and annotations cover the safety profile. The description supplies the non-idempotency behavior, the privacy scope, and the population path, which is everything needed to call it correctly. Only the absence of explicit guidance on update/delete alternatives keeps it at 4.

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%: the name and description parameters, including their length limits, are already fully documented in the schema. The description adds no syntax, default, or formatting detail beyond that. Baseline 3 is correct when the schema carries parameter meaning.

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?

States a specific verb and resource ("Creates a private collection") plus the outcome ("returns it with its collection id") and the collection's role (sorting saved ads). It also distinguishes its role from save_ad/move_saved_ad, which populate rather than create. It does not explicitly contrast with update_collection or list_collections, keeping it just short of a 5.

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 context for use (grouping saved ads) and routes the population step to the sibling tools save_ad and move_saved_ad. The duplicate-name warning ("Each call creates a new collection, even when the name repeats") is a useful usage caveat. No explicit when-not-to-use or alternative for renaming/merging exists, so it is not a 5.

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