ppt-mcp

ppt_list_jobs

Lists recent PDF-to-PPT conversion jobs, displaying status and details so you can monitor progress and results.

Instructions

List recent conversion jobs from the wrapped local ppt API.

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": "ppt_list_jobs"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 2, 2026

TDQS

B3.1/5.0

Behavior2/5

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

With no annotations provided, the description must disclose behavioral traits, but it only states the core function. It does not mention that the operation is read-only, nor does it explain ordering (e.g., 'recent' by time), pagination, or the effect of the optional limit parameter. The description adds minimal behavior beyond the tool's name.

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 a single sentence with no redundant wording. It is front-loaded and appropriately sized for the minimal information it contains, making every word purposeful.

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?

Given the simple interface (one optional parameter) and presence of an output schema, the description should at least clarify the behavior of the limit parameter and the meaning of 'recent'. Without these details, the description is incomplete for an agent to predict the tool's full behavior, even though the output schema may cover return structure.

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

Parameters1/5

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

The schema has one parameter 'limit' with no description, and schema description coverage is 0%. The description fails to explain the meaning or effect of 'limit', nor does it mention any parameter at all, leaving the agent to infer semantics solely from the parameter name.

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 explicitly states the action ('List') and the resource ('recent conversion jobs') with a specific source ('wrapped local ppt API'). This clearly distinguishes it from sibling tools like ppt_get_job_status, which target individual jobs.

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 description implies its usage as a listing operation but provides no explicit guidance on when to choose it over alternatives, nor does it mention any exclusions or related tools. The name and action make the primary use clear, but no comparative context is given.

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

Deploy Server