Generate an ig.me short link that opens Instagram DMs directly with a tracking or referral payload, so you can route users to a specific DM with campaign tags.
Generate an ig.me short link (https://ig.me/m/in.yogeshwar?ref=...) that opens Instagram DMs directly with a tracking/referral payload.
| Name | Required | Description | Default |
|---|---|---|---|
| ref_payload | No | Optional referral code/tag (e.g., "free_guide", "bio_link", "yt_video"). |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden. It discloses the output URL format and that the link embeds a tracking/referral payload, which is useful, but it does not mention authentication requirements, link lifetime, whether tracking is recorded, or what exactly is returned beyond an example URL.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The definition is a single front-loaded sentence with no wasted words. It puts the core action and output format first and includes only essential context.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple one-parameter utility with no output schema, the description is mostly sufficient to invoke the tool, but it leaves gaps around usage context and runtime behavior. It should clarify when to choose this over sending a direct message and what the returned value actually looks like.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the single optional ref_payload parameter is already documented in the schema. The description reinforces its purpose by showing a ref example in the URL, but it adds no syntax or semantic detail beyond what the schema provides.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description gives a specific verb ("Generate"), a precise resource ("ig.me short link"), and clarifies its behavior (opens Instagram DMs with a tracking/referral payload). This clearly distinguishes it from siblings like send_instagram_dm, which sends a message rather than generating a link.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description explains what the link does but does not say when an agent should use this tool versus alternatives such as send_instagram_dm or other messaging tools. No prerequisites, exclusions, or contextual guidance are provided.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.