PhotoForge MCP Server

export_to_notion

Create a Notion page for a fashion shoot log or marketing brief from a media asset URL, page title, and production notes.

Instructions

Create a fashion shoot log or marketing brief in Notion.

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>",
      "pageTitle": "<pageTitle>"
    },
    "name": "export_to_notion"
  }
}

Input Schema

Name	Required	Description
`notes`	No	Production notes.
`assetUrl`	Yes	Media asset URL.
`pageTitle`	Yes	Notion page title.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Oct 24, 2026

TDQS

B3.1/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 behavioral burden. It states that a Notion page is created, but does not disclose permissions, side effects, failure behavior, or what is returned after creation.

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?

The description is a single front-loaded sentence with no wasted words. It is appropriately sized for a short tool definition.

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?

The input schema fully documents the parameters, which helps completeness. However, for a mutation tool with no annotations and no output schema, the description omits behavioral details such as authentication needs, side effects, and result shape.

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%, so all three parameters are already documented in the input schema. The description adds no parameter-specific meaning beyond the schema, which is acceptable given full schema coverage.

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 specific verb and target platform: create a fashion shoot log or marketing brief in Notion. It is clear what kind of artifact is produced, though it does not explicitly distinguish this from sibling export tools such as export_to_shopify or export_to_social.

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 gives no explicit guidance on when to choose this tool instead of alternatives. It implies a Notion export use case but does not mention sibling tools or conditions that select this destination.

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