Skip to main content
Glama
Sign In

ContentSweep Supplier Feeds

by ai.contentsweep
OverviewDiscussionsAdmin

delete_supplier_feed_profile

DestructiveIdempotent

Permanently delete an owned saved profile after explicit operator instruction. This does not start an evaluation or use credits.

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

Input Schema

NameRequiredDescriptionDefault
profile_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already carry destructiveHint=true and idempotentHint=true, so the safety profile is known. The description adds real value beyond them: permanence (irreversibility), the ownership constraint on the target, the operator-confirmation requirement, and the fact that no evaluation runs and no credits are spent.

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?

Two short sentences with no filler; the destructive action and its precondition are front-loaded, and the credit/evaluation caveat follows as a targeted disambiguation.

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 one-parameter destructive tool with no output schema and full annotation coverage, the description supplies the essential context: permanence, ownership, operator confirmation, and cost neutrality. It omits failure behavior (e.g., profile not found or not owned by the caller), which is the only notable gap.

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?

The single parameter profile_id has 0% schema description coverage, so the schema contributes nothing about its format or expected value. The description only implies the target must be an owned saved profile and adds no identifier syntax, so it partially but not fully compensates for the coverage gap.

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 ("Permanently delete an owned saved profile") and scopes it to profiles owned by the caller. It is unambiguous against the siblings, none of which delete, though it does not explicitly name which sibling to use for the softer alternatives.

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 a clear precondition ("after explicit operator instruction"), which is exactly the gate an agent needs before a destructive call. It also disambiguates from start_supplier_import and quote_supplier_import by saying this does not start an evaluation or consume credits, though it does not describe what to do if the operator wants to merely deactivate a profile instead.

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

All ContentSweep Supplier Feeds 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