Skip to main content
Glama
Sign In

Mobbin

by com.mobbin
OverviewDiscussionsAdmin

Add Comment

add_comment

Add a comment to a screen, flow or website section for the user's Mobbin MCP connection, such as why the user saved it. The user and their teammates see it on Mobbin, and get_collection_contents returns it. Use an id from another Mobbin tool's result, like search or get_collection_contents, or the id (a UUID) in a Mobbin link the user shares. Never guess or make up an id. Use it only when the user asks to comment on or add a note to an item. An item that isn't saved yet is saved to All saved first. Mobbin adds a line saying which app posted the comment, so don't sign it. Each call posts a new comment, so send each note once. @mentions aren't supported. If the user wants to mention a teammate, tell them first that no one will be notified and the mention stays plain text.

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": {
      "content_id": "<content_id>",
      "content_type": "<content_type>",
      "comment": "<comment>"
    },
    "name": "add_comment"
  }
}

Input Schema

NameRequiredDescriptionDefault
commentYesPlain text. Line breaks are kept. @mentions don't notify anyone.
content_idYesA screen, flow or section id.
task_intentNoOne short sentence summarizing the user's overall task. Helps return more relevant results. Write it in English even when the conversation is in another language. MUST be the same across all calls for the same task. Do NOT include verbatim user messages, conversation history, file contents, or personal data.
content_typeYes

Output Schema

NameRequiredDescriptionDefault
mobbin_urlYesLink to the content item on Mobbin, where the comment shows.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations cover readOnly/idempotent flags, but the description adds substantial context beyond them: an unsaved item is first saved to All saved, each call posts a new comment (so don't re-send), Mobbin appends an attribution line (so don't sign), and no one is notified by @mentions. These are exactly the secondary effects an agent could otherwise get wrong.

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?

Information is well front-loaded — purpose, then id sourcing, then usage boundary, then side effects. It is on the long side, and the @mention caveat is partly duplicated by the schema's comment description, so a small amount could be trimmed.

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

Completeness5/5

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

For a 4-parameter write tool with an output schema and annotations, the description covers everything an agent needs: valid id provenance, the auto-save side effect, non-idempotency, mention limitations, and where the comment later surfaces. Nothing required to call it correctly is missing.

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

Parameters4/5

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

With 75% schema coverage the baseline is 3, and the description earns a bump by explaining where content_id values legitimately come from and that it must be a UUID from a tool result or link. It says nothing extra about task_intent or content_type beyond the schema's enum and description, so it is not a full 5.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource ("Add a comment to a screen, flow or website section") and names the exact id sources, so the agent knows this is a write-comment tool, not a save/search tool. It also distinguishes itself from siblings by never overlapping with save_content, create_collection, or the search tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit routing: "Use it only when the user asks to comment on or add a note to an item" gives both the trigger and an implicit exclusion. It also states where valid ids come from (another Mobbin tool's result, or a UUID in a shared link) and warns "Never guess or make up an id."

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

All Mobbin toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources