Skip to main content
Glama

550W AI去字幕去水印

list_image_watermark_tasks

Read-onlyIdempotent

List your account image tasks. Page numbering starts at 1.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_image_watermark_tasks"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo
sizeNo
orderNo
statusNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds one useful convention (page numbering starts at 1), but says nothing about defaults, ordering direction, or what status values mean when omitted.

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?

Two short sentences, front-loaded with the resource being listed and no filler. The second sentence is small but relevant, so nothing is wasted, though the definition is arguably too terse for its parameter surface.

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

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With four undocumented parameters, no output schema, and no explanation of pagination limits or result shape, the definition leaves large gaps for an agent that must paginate and filter correctly. It does not describe what a task record contains or how to detect more pages.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must carry parameter meaning and it largely doesn't. Only the page numbering convention is clarified (and the schema already enforces minimum 1); size, order, and status — including whether status defaults to 'all' — 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 ('List ... image tasks') and scopes it to the caller's account. The 'image' qualifier implicitly separates it from siblings like list_media_tasks and list_subtitle_tasks, though neither alternative is named.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

No guidance on when to use this listing versus get_image_watermark_task (single-item lookup) or the broader list_media_tasks. There are no stated prerequisites or exclusions; usage must be inferred from the tool name alone.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources