SendIt

Request Project Content

request_project_content

Generate UGC, slideshow, remix, caption, or calendar content from project intelligence.

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": {
      "projectId": "<projectId>"
    },
    "name": "request_project_content"
  }
}

Input Schema

Name	Required	Description
`goal`	No
`count`	No
`prompt`	No
`team_id`	No	Optional team ID or slug. Ignored when using a team-scoped API key.
`platforms`	No
`projectId`	Yes
`contentType`	No
`saveToLibrary`	No
`consentConfirmed`	No	Required when using uploaded creator or likeness-like media.

Schema Changelog

Changes observed during successful MCP inspections.

First observedMay 5, 2026

TDQS

C2.9/5.0

Behavior3/5

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

With annotations indicating readOnlyHint=false and openWorldHint=true, the description adds a little context by listing output types, but it does not disclose behaviors such as whether content is saved to the library, non-determinism of AI generation, or associated costs. Annotations cover the basic safety profile, but the description adds minimal additional behavioral transparency.

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 a single concise sentence with a clear front-loaded verb ('Generate') and specific content types. It is efficient, though it could include more useful detail without becoming verbose.

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?

The tool has 9 parameters, no output schema, and very low schema coverage. The description is far too brief to provide adequate context about what 'project intelligence' means, what the output looks like, or how parameters interact. It leaves critical gaps for an agent to correctly invoke the tool.

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 only 22%, with most parameters lacking descriptions. The description partially maps to the contentType enum ('UGC, slideshow, remix, caption, calendar') but provides no meaning for other key parameters like prompt, count, platforms, or saveToLibrary. Since schema coverage is low, the description should compensate but does not.

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 tool generates specific content types (UGC, slideshow, remix, caption, calendar) using project intelligence. It identifies the action and resource but does not explicitly distinguish it from sibling tools like 'generate_content' or 'generate_post_bundle', so it misses the top score for sibling differentiation.

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 guidance on when to use this tool versus alternatives such as 'generate_content' or 'save_project_content_to_library'. No context, prerequisites, or exclusions are provided. The description only implies it is for generating content based on project data, which is not enough to guide tool selection.

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

All SendIt tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.