QR for Agent

update_social_qr

Update social media links on a Social QR code by specifying new URLs. Partial updates merge with existing data, allowing selective changes without resetting other links.

Instructions

Update the social media links of a Social QR code. Partial updates merge with existing data.

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": {
      "short_id": "<short_id>"
    },
    "name": "update_social_qr"
  }
}

Input Schema

Name	Required	Description
`short_id`	Yes	The short ID of the Social QR code to update.
`facebook`	No	Facebook URL.
`instagram`	No	Instagram URL.
`twitter`	No	Twitter/X URL.
`linkedin`	No	LinkedIn URL.
`youtube`	No	YouTube URL.
`tiktok`	No	TikTok URL.
`github`	No	GitHub URL.
`website`	No	Website URL.
`label`	No	Update the label.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Mar 30, 2026

TDQS

B3.2/5.0

Behavior3/5

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

No annotations are provided. The description adds one behavioral trait: 'Partial updates merge with existing data', which is useful. However, it lacks disclosure of other behaviors such as authentication requirements, rate limits, or side effects, so the burden is partially met.

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

Conciseness4/5

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

The description is two sentences, front-loaded with the verb and resource. Every word serves a purpose. Minor improvement could merge the second sentence for even tighter structure, but it is already concise.

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?

No output schema exists, and the description does not mention return values, errors, or permissions. For a mutation tool with 10 parameters (all but one optional), the description is minimally adequate but lacks completeness for safe autonomous invocation.

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 already describes all parameters with 100% coverage. The tool description does not add extra meaning beyond 'partial updates merge', so it meets the baseline. No param-specific enrichment is present.

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 clearly states the verb 'Update' and the resource 'Social QR code', specifying that it updates social media links. The mention of partial merge adds specificity but does not explicitly differentiate from sibling tools like update_vcard_qr or update_qr_destination.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus other update tools (e.g., update_app_store_qr, update_vcard_qr). It does not mention alternatives or prerequisites, leaving the agent to infer usage from context alone.

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