JobMojito

Create custom report

create_report

Destructive

[Reports] Save a new custom report from a definition (schema jobmojito.report/v1). It is created as Only me: tell the user they can share it from the returned admin_url. Check the definition with preview_report first.

Stores a new custom report. It is created as "Only me" (private to you); share it from the JobMojito admin. Returns its id, version and the admin link to open it. Check the definition with preview_report first.

Input Schema

TableJSON Schema

Name	Required	Description
`definition`	Yes	A custom report: report-wide filters and up to 12 blocks. Read report-catalog first for the dataset, field and measure ids.
`merchant_id`	No	Optional merchant to act on. Admins and sub-merchant operators only; other callers always use their token's merchant.
`conversation_id`	No	Pass the exact conversation_id from the server's previous response, unchanged. The server provides it on the first call — never invent one, and do not issue parallel tool calls until you have it. Keep passing the same conversation_id for the rest of the conversation, including after later user messages or on a different task; do not reset it when the user starts a new request.

Output Schema

TableJSON Schema

Name	Required	Description
`id`	Yes
`version`	Yes	Send it back with the next update.
`admin_url`	Yes	Open the report in the JobMojito admin.
`published`	Yes	false when the change was stored as a draft the owner publishes in the admin.
`_mcp_instructions`	No	Server-issued metadata for this conversation.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 19, 2026

changedInput schema / properties / definition / properties / filters / properties / interview_ids / description

Previous value: -"Only these interviews (interview ids from list_interviews). Empty or missing = all."New value: +"Interviews to show (interview ids from list_interviews), combined with the other picks by OR. Nothing picked = all."

changedInput schema / properties / definition / properties / filters / properties / position_ids / description

Previous value: -"Only these positions (position ids from list_interviews). Empty or missing = all."New value: +"Positions to show (position ids from list_interviews). position_ids, interview_ids and without_position are one pick list: a row shows when it belongs to ANY pick. Nothing picked = all."

addedInput schema / properties / definition / properties / filters / properties / without_position

Added value: +{
+  "description": "Also pick interviews that are not part of any position (stand-alone interviews, and coaching sessions). Combined with the other picks by OR.",
+  "type": [
+    "boolean",
+    "null"
+  ]
+}

AddedOct 18, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=true and idempotentHint=false. The description adds genuinely new behavior: the report is created private ('Only me'), it can be shared later from the admin, and the response carries id, version and admin_url — plus a directive to tell the user about sharing.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The body is duplicated almost verbatim — the 'Only me' privacy note and the preview_report instruction each appear twice, and the second paragraph restates the first wholesale. Front-loading is fine, but half the text fails to earn its place.

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

Completeness4/5

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

For a create tool with an output schema, the description covers the essentials an agent needs: the payload schema, the validation prerequisite, the default privacy state, and the share path. The destructive annotation is never explained, which is a minor remaining gap.

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 the schema already documents definition, merchant_id and conversation_id in depth, including nested block semantics. The description adds no parameter meaning beyond restating the definition's schema id, so baseline 3 applies.

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?

States a specific verb and resource ('Save a new custom report from a definition') and pins the payload contract ('schema jobmojito.report/v1'). An agent can distinguish this from preview_report, update_report and run_report without opening a schema.

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

Usage Guidelines4/5

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

Explicitly routes the agent to preview_report first ('Check the definition with preview_report first'), which is a real prerequisite. It does not, however, say when to prefer update_report over creating a new report, so one gap remains.

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

All JobMojito 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.