PhotoForge MCP Server

export_to_social

Publish and schedule photos or videos to chosen social platforms using a media asset URL, with optional caption and channel selection.

Instructions

Export and schedule photos and videos to social platforms.

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": {
      "assetUrl": "<assetUrl>"
    },
    "name": "export_to_social"
  }
}

Input Schema

Name	Required	Description
`caption`	No	Post caption.
`assetUrl`	Yes	Media asset URL.
`channels`	No	Target social platforms.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Oct 24, 2026

TDQS

C2.9/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 says 'export and schedule' but never states whether the export happens immediately, what a scheduled post requires, whether authentication on the target platforms is needed, whether operations are reversible, or how failures on one channel are reported. For an external, side-effecting publishing tool this is a substantial gap.

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?

A single front-loaded sentence with the verb and resource up front and no wasted words. It is efficient, though brevity here comes at the cost of needed behavioral detail rather than being purely a virtue.

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

Completeness2/5

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

For a publishing tool with no annotations, no output schema and an unenumerated free-text channels array, the description should say which platform values are accepted and what happens on schedule vs immediate export. None of that is present, so the agent lacks what it needs to call the tool confidently.

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 description coverage is 100% (caption, assetUrl, channels), so the schema already documents all three parameters and the baseline is 3. The description adds no syntax or constraint detail, and notably implies scheduling although no schedule-time parameter exists, which could mislead an agent about what it must supply.

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 names a concrete verb pair (export/schedule) and the resource (photos and videos) plus the destination class (social platforms), so the agent can tell it apart from the Shopify, Notion and Fanvue exporters at a high level. It does not say which social platforms are supported or how this differs from export_to_fanvue, which is itself a social platform, leaving the boundary slightly fuzzy.

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?

There is no statement of when to use this tool versus export_to_fanvue or the other export siblings, no prerequisites, and no exclusions. The agent must infer from the tool name that this is the multi-platform social path.

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