pressadvantage-mcp

add_first_release_keyword

Add a keyword to the first release within a scheduled order. Specify the scheduled order ID and keyword, with an optional URL for linking.

Instructions

Add a keyword specifically for the first release in a scheduled 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>",
      "keyword": "<keyword>"
    },
    "name": "add_first_release_keyword"
  }
}

Input Schema

Name	Required	Description
`url`	No	URL to link this keyword to
`keyword`	Yes	Keyword for the first release
`scheduled_order_id`	Yes	Scheduled release order ID

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 1, 2026

TDQS

A3.8/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden. It only states the action without disclosing side effects, permissions, idempotency, or error behavior. As a mutation tool, it lacks necessary behavioral context.

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, concise sentence that is front-loaded with the action and scoping information. Every word earns its place.

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

Completeness4/5

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

Given the low complexity of the tool and complete schema descriptions, the description is sufficient for an agent to understand the tool's purpose and parameters. However, behavioral details are missing, but that is already addressed in the transparency dimension.

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 each parameter having a description. The tool description adds minimal extra context about the 'first release' purpose but does not enhance parameter understanding beyond the schema.

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 clearly states the action ('Add a keyword') and the specific scope ('for the first release in a scheduled order'). This distinguishes it from the sibling tool 'add_scheduled_keyword' by specifying the first release context.

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

Usage Guidelines4/5

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

The description provides a clear context for when to use the tool (specifically for the first release in a scheduled order) but does not explicitly state when not to use it or mention alternatives like 'add_scheduled_keyword'.

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