pressadvantage-mcp

add_scheduled_image

Attach an image to a scheduled press release order using the scheduled order ID and image URL. Optionally include alt text for the image.

Instructions

Attach an image to a scheduled release order

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": {
      "scheduled_order_id": "<scheduled_order_id>",
      "url": "<url>"
    },
    "name": "add_scheduled_image"
  }
}

Input Schema

Name	Required	Description
`alt`	No	Alt text for the image
`url`	Yes	Image URL
`scheduled_order_id`	Yes	Scheduled release order ID

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 1, 2026

TDQS

A3.5/5.0

Behavior2/5

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

No annotations are provided, and the description only states the action without detailing side effects, such as whether the image replaces existing images, permission requirements, or what is returned. This leaves significant behavioral ambiguity for a mutation tool.

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, clear sentence with no filler or redundant information. It is highly concise and front-loaded, with every word earning its place.

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?

The tool is simple and the schema fully documents all parameters. However, the lack of annotations and output schema means the description must cover behavioral context; it provides only the basic action, leaving gaps about multiple images and error behavior. It is minimally adequate but incomplete.

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 100%, with descriptions for scheduled_order_id, url, and alt. The description adds no additional parameter semantics beyond what the schema already provides, so a baseline score of 3 is appropriate.

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 uses a specific verb 'Attach' and clearly identifies the resource 'an image to a scheduled release order'. This differentiates it from sibling tools like add_scheduled_video and add_scheduled_subject.

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 by clearly stating the action, but it does not explicitly mention when to use it or contrast it with alternatives. No prerequisites or conditions are provided.

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