pressadvantage-mcp

update_organization

Update an organization's profile, including contact details, about text, website, and social handles, to keep press room information accurate for media outreach.

Instructions

Update an existing organization

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": {
      "id": "<id>"
    },
    "name": "update_organization"
  }
}

Input Schema

Name	Required	Description
`id`	Yes	Organization ID to update
`name`	No	Name of the organization
`address`	No	Physical address
`about_text`	No	Short description about the organization
`twitter_id`	No	Twitter/X handle (without @)
`facebook_id`	No	Facebook page ID or handle
`website_url`	No	Organization website URL
`contact_name`	No	Primary contact full name
`contact_email`	No	Primary contact email address
`contact_phone`	No	Primary contact phone number
`show_website_in_iframe`	No	Embed website in iframe on press room page
`show_on_pressadvantage_homepage`	No	Feature organization on the PA homepage

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 1, 2026

TDQS

C2.3/5.0

Behavior1/5

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

With no annotations, the description carries full behavioral disclosure burden. It only says 'Update an existing organization' without revealing whether the update is partial or full, required permissions, idempotency, or return value. This is a minimal mutation tool with zero transparency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise at five words and is not verbose. However, it is under-specified; it lacks structure and does not front-load any actionable information beyond what the tool name implies.

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

Completeness1/5

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

This mutation tool has 12 parameters, no annotations, no output schema, and a large sibling set, yet the description fails to explain partial update semantics, response behavior, or usage context. It is entirely inadequate for an agent to select and invoke the tool correctly.

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?

The input schema provides 100% coverage with descriptive comments for all 12 parameters, so the baseline is 3. The description itself adds no parameter-level context, but the schema already handles parameter semantics adequately.

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?

The description states the core action ('Update') and resource ('organization'), clearly distinguishing it from create or delete operations. However, it lacks scope or context (e.g., which fields can be updated) and does not explicitly differentiate from related tools like get_organization.

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

Usage Guidelines1/5

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

No guidance is provided on when to use this tool versus alternatives. It does not mention prerequisites (e.g., 'organization must already exist'), partial update behavior, or how it differs from create_organization or get_organization.

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