Skip to main content
Glama
Foto MCP Server
by thesven

foto_report_content

Submit a community safety moderation report for a Foto post or user, specifying target type, ID, and reason to flag spam, harassment, copyright, or undisclosed AI content.

Instructions

Submit a community safety moderation report for a post or user on Foto.

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": {
      "targetType": "<targetType>",
      "targetId": "<targetId>",
      "reason": "<reason>"
    },
    "name": "foto_report_content"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonYesPrimary reason for the report (e.g. 'spam', 'ai_generated_undisclosed', 'harassment', 'copyright')
detailsNoOptional additional context
targetIdYesThe postId or userId being reported
targetTypeYesWhether reporting a 'post' or a 'user'

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.0.1

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, and it says nothing about side effects beyond the word 'Submit'. It does not state whether the report is anonymous, whether the reported user is notified, whether duplicate reports are rejected, what permissions or authentication are required, or what the caller gets back. For a mutation tool with zero annotation coverage this is a substantial omission.

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?

A single front-loaded sentence with no filler; the action and target scope are stated first and nothing is redundant.

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 tool is simple (4 flat parameters, fully documented schema, no output schema), so the definition is minimally viable. However, for an unannotated write operation the description should at least indicate the outcome of a successful submission or any precondition, which it does not.

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%, with per-field descriptions and an enum for targetType, so the schema already does the semantic work. The description only echoes the 'post or user' distinction from targetType and adds no extra meaning about the accepted reason vocabulary or how targetId should be formed.

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 uses a specific verb and resource: 'Submit a community safety moderation report', and names the two possible targets ('a post or user'). An agent can tell what the tool does immediately, though it does nothing to distinguish itself from siblings (there is no other moderation/report tool in the sibling list, so this is a minor gap).

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?

Usage is only implied by the words 'community safety moderation report' — an agent must infer that this is the tool for flagging abusive or non-compliant content. There is no guidance on when to prefer it over other actions (e.g., deleting a comment vs. reporting it), no prerequisites such as being logged in, and no note on what to do if the same content was already reported.

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