Hook Detector

edit_thumbnail

Edit one thumbnail (an image of your thumbnails call, or a picture you send): op erase, edit, face_swap, text, text_variations, upscale, fix, crop or color. crop and color are free; upscale 12; the rest 4 (a version each for text_variations), charged only for what is delivered. Answers at once; read it with get_thumbnails. Same as POST /v1/thumbnails/edit.

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

Input Schema

Name	Required	Description
`op`	Yes
`faces`	No
`fixes`	No
`words`	No
`prompt`	No
`region`	No
`source`	No
`api_key`	No
`contrast`	No
`source_n`	No
`brightness`	No
`saturation`	No
`variations`	No
`score_call_id`	No
`source_call_id`	No
`idempotency_key`	No	1 to 255 visible ASCII characters; the same key and request within 24 hours answer the saved remix and charge nothing; the same key with another request is 422 idempotency_key_reused

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 26, 2026

TDQS

B3.4/5.0

Behavior3/5

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

With no annotations, the description carries the full burden; it does add real behavioral value by disclosing credit costs per op (crop/color free, upscale 12, others 4) and that billing applies only to delivered output. It does not state authentication needs, what happens to the original thumbnail (overwrite vs new version), or error behavior beyond what the schema's idempotency_key field already says.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the verb and the op list, then cost, then result retrieval and the REST equivalent. Dense but every sentence carries information; slight run-on feel from cramming pricing into the first paragraph.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 formats need not be described, and the tool is correctly pointed at get_thumbnails for results. However, for a 16-parameter tool, the absence of any op→parameter mapping leaves an agent guessing how to construct a valid call.

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 only 6% across 16 parameters, so the description must compensate. The op names hint at the parameter families (face_swap→faces, fix→fixes, text→words, edit→prompt, crop→region, color→contrast/brightness/saturation), but this mapping is never stated, and source, source_call_id, source_n, score_call_id and variations are left unexplained.

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 ('Edit one thumbnail') and enumerates the exact operations available (erase, edit, face_swap, text, text_variations, upscale, fix, crop, color). It does not explicitly contrast with the nearby siblings make_thumbnails or recreate_thumbnail, so differentiation is only partial.

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?

The op list implies when each mode is used, and it correctly points to get_thumbnails to read the result. But there is no guidance on when to prefer this over make_thumbnails/recreate_thumbnail, and no statement of which parameters are required for which op.

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

All Hook Detector tools Inspect

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

Need Help?