Apdf — PDF Tracking & Analytics

Create Automation

create-automation

Create a when/filter/then rule that posts reader events to a webhook. The automation starts out active.

Input Schema

TableJSON Schema

Name	Required	Description
`name`	Yes	Human-readable name for the automation.
`scope`	No	Which documents to watch. Defaults to "all".
`events`	Yes	Reader events that trigger the automation, matched with OR. Pass "*" as the only entry to trigger on every event.
`doc_ids`	No	Public ids of the documents to watch. Required when "scope" is "specific", ignored otherwise.
`conditions`	No	Filters that must all pass before the webhook fires. Not available for an "*" automation.
`webhook_url`	Yes	URL that receives the POST request when the automation fires.
`webhook_headers`	No	Additional headers for the webhook request, as header name => value.

TDQS

A3.9/5.0

Behavior4/5

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

Discloses key behavior: 'The automation starts out active.' This adds value beyond the annotations (only destructiveHint=false). No contradictions. Could mention if automation is immediately triggered, but still good.

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 sentences, highly efficient. First sentence states purpose, second adds important behavioral detail. No filler.

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?

Given the tool's complexity (7 parameters, nested objects, no output schema), the description is somewhat minimal. Does not explain return values or side effects. Sufficient for simple creation but lacks depth.

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%, so baseline is 3. Description summarizes the rule structure but does not add new details beyond what the schema already provides for parameters.

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?

Specifically describes the tool's function: 'Create a when/filter/then rule that posts reader events to a webhook.' Clearly distinguishes from sibling tools like activate-automation, deactivate-automation, delete-automation.

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?

Implies usage when setting up an automation that sends webhook based on reader events. Lacks explicit guidance on when not to use or mention of alternatives like updating an existing automation. Sufficient but not thorough.

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

All Apdf — PDF Tracking & Analytics tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.8/5.0

Disambiguation5/5

Each tool targets a distinct operation (document management, PDF manipulation, automation, analytics, etc.) with clear boundaries, making it easy for an agent to select the correct one.

Naming Consistency5/5

All tool names follow a strict lowercase-with-hyphens pattern and use consistent verb-noun phrasing (e.g., 'create-document', 'list-documents', 'add-pdf-security'), ensuring predictability.

Tool Count2/5

At 45 tools, the server far exceeds the recommended 3-15 range for a well-scoped set. While the coverage is comprehensive, the high number may overwhelm agents and suggests insufficient consolidation.

Completeness5/5

The tool surface covers the full lifecycle of documents and PDFs—creation, retrieval, update, deletion, archiving, security, OCR, splitting, merging, automation, analytics, and more—with no obvious gaps.

Resources

Need Help?