Skip to main content
Glama

instagram_upload

Destructive

Attach explicitly requested, staged image or video files to an observed Instagram file input for upload preparation; this does not publish the content.

Instructions

Attach explicitly requested image/video files staged under the private uploads folder to an observed file input. Upload is not publication.

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": {
      "ref": "<ref>",
      "files": "<files>",
      "expected_account": "<expected_account>"
    },
    "name": "instagram_upload"
  }
}

Input Schema

NameRequiredDescriptionDefault
refYes
filesYes
expected_accountYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and idempotentHint=false, so the description is not the sole source of the safety profile. It does add real value by clarifying that files must already be staged in a private uploads folder and that the action does not publish, but it never explains what the destructive aspect means (e.g., whether an existing input's value is replaced) or what authorization/account constraints apply.

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?

Two short sentences, front-loaded with the action, with the key disambiguation ('not publication') placed as a closing clarifier. Nothing is wasted.

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?

An output schema exists, so return values need no explanation. But with three required parameters at 0% schema coverage and a destructive annotation, the definition leaves the two most opaque parameters and the destructive consequence undocumented.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must carry parameter meaning. It only clarifies 'files' (image/video, must be staged in the uploads folder); 'ref' and 'expected_account' are never explained, and the account-mismatch behavior implied by 'expected_account' is left entirely unstated.

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?

States a specific verb and resource: attaching image/video files to an observed file input. The closing line 'Upload is not publication' implicitly separates it from instagram_post_image, though no sibling is named explicitly.

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?

'Explicitly requested' and 'staged under the private uploads folder' imply preconditions for use, and 'Upload is not publication' implies a when-not boundary. However, it never names instagram_post_image or instagram_fill as the alternative to use for publishing or form filling, so the routing is left to inference.

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