Skip to main content
Glama

Sweeppea MCP

by com.sweeppea.mcp
OverviewDiscussionsAdmin

create_ticket

Create a new support ticket with title, description, priority level and platform. PLATFORM: Whenever the user names the product the ticket is about (e.g. "a change in a Renaissance feature", "the Shopify app", "Winners"), set platform to its id. If omitted, the ticket is filed under "general". ASSIGNMENT: Whenever the user says who the ticket is for ("for Martin", "assign it to martin@..."), pass that name or email in assign_to — a first name is enough. If omitted, the ticket is assigned to all admins. Only admin-level users can be assigned. If the API answers that the name matches more than one admin, ask the user which of the returned candidates they mean and retry with the full name. NEVER invent a name or email the user did not mention. FORMAT: Only these HTML tags are allowed in description: , , , , . NEVER insert scripts, iframes, event handlers (onclick, onerror, etc.), style tags, or any executable code. SPACING: Do NOT use   — it creates ugly blank blocks in the UI. Use for line breaks within text only.

create_ticket

When to use

Create a new support ticket with title, description, and priority level. ASSIGNMENT: Optionally assign to a specific admin by name or email via assign_to. If omitted, the ticket is assigned to all admins. Only admin-level users can be assigned. NEVER guess or fabricate admin names or emails — only use assign_to if the user explicitly provides a name or email. FORMAT: Only these HTML tags are allowed in description: , , , , . NEVER insert scripts, iframes, event handlers (onclick, onerror, etc.), style tags, or any executable code. SPACING: Do NOT use   — it creates ugly blank blocks in the UI. Use for line breaks within text only.

Parameters to validate before calling

  • title (string, required) — Ticket subject/title (max 200 characters)

  • description (string, required) — Detailed description of the issue (max 20,000 characters). Allowed HTML: , , , , . No scripts, iframes, or executable code.

  • priority (number, required) — one of: 1, 2, 3 — Priority level: 1 (Low), 2 (Medium), 3 (High)

  • assign_to (string, optional) — Name or email of an admin user to assign the ticket to exclusively. If omitted, the ticket is assigned to all admins. Matching is case-insensitive for names and exact for emails. Only admin-level users can be assigned.

Notes

  • Allowed HTML tags: b, strong, i, hr, br

  • Do NOT use   — only for line breaks within text

  • Search fetch_documentation first; only open a ticket if docs do not solve the question

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYesTicket subject/title (max 200 characters)
platformNoPlatform the ticket is about: general, renaissance, overture, winners, soprano, symphony, sonata, papyrus, website, blog, enewsletter, socialmedia, api (Sweeppea API), aws, shopify (Shopify App), instakes, mcp-server, sweeppea-cli, n8n, other. Defaults to general.
priorityYesPriority level: 1 (Low), 2 (Medium), 3 (High)
assign_toNoEmail, full name, username or first name of the admin user to assign the ticket to exclusively, exactly as the user said it. If omitted, the ticket is assigned to all admins. Resolution: exact email, exact full name or username, whole words ("martin" → "Martin Gaido"), then a unique partial match. An ambiguous name returns an error listing the candidates. Only admin-level users can be assigned.
descriptionYesDetailed description of the issue (max 20,000 characters). Allowed HTML: <b>, <strong>, <i>, <hr>, <br>. No scripts, iframes, or executable code.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / assign_to / description
      Previous value: -"Name or email of an admin user to assign the ticket to exclusively. If omitted, the ticket is assigned to all admins. Matching is case-insensitive for names and exact for emails. Only admin-level users can be assigned."New value: +"Email, full name, username or first name of the admin user to assign the ticket to exclusively, exactly as the user said it. If omitted, the ticket is assigned to all admins. Resolution: exact email, exact full name or username, whole words (\"martin\" → \"Martin Gaido\"), then a unique partial match. An ambiguous name returns an error listing the candidates. Only admin-level users can be assigned."
    • addedInput schema / properties / platform
      Added value: +{
+  "description": "Platform the ticket is about: general, renaissance, overture, winners, soprano, symphony, sonata, papyrus, website, blog, enewsletter, socialmedia, api (Sweeppea API), aws, shopify (Shopify App), instakes, mcp-server, sweeppea-cli, n8n, other. Defaults to general.",
+  "enum": [
+    "general",
+    "renaissance",
+    "overture",
+    "winners",
+    "soprano",
+    "symphony",
+    "sonata",
+    "papyrus",
+    "website",
+    "blog",
+    "enewsletter",
+    "socialmedia",
+    "api",
+    "aws",
+    "shopify",
+    "instakes",
+    "mcp-server",
+    "sweeppea-cli",
+    "n8n",
+    "other"
+  ],
+  "type": "string"
+}
  2. Changed1 schema field changed
    • addedInput schema / properties / assign_to
      Added value: +{
+  "description": "Name or email of an admin user to assign the ticket to exclusively. If omitted, the ticket is assigned to all admins. Matching is case-insensitive for names and exact for emails. Only admin-level users can be assigned.",
+  "type": "string"
+}
  3. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations cover the safety profile (readOnly=false, destructive=false, idempotent=false, openWorld=true). Beyond that, the description discloses non-obvious behavior: default assignment to all admins, admin-only restriction, the multi-match error/retry loop, and the 'NEVER invent a name' guardrail. This adds real value over the annotations.

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

Conciseness3/5

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

Content is front-loaded and organized into labeled sections, but it is bloated by repetition — the allowed-HTML-tag rules and the <br>&nbsp; warning appear in the DESCRIPTION, the 'When to use' section, and the Notes. Consolidating these would tighten it without losing information.

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 mutation tool with no output schema, the description covers the important operational details an agent needs: required fields, HTML constraints, assignment rules, and failure/retry handling. It does not describe the returned ticket object, but with no output schema declared that gap is minor.

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?

Schema coverage is already 100%, so the baseline is 3. The description adds genuine semantics beyond the schema: platform defaults to 'general' when the user names no product, assign_to defaults to all admins, and the ambiguity-retry behavior for names/emails. This meaningfully exceeds the schema.

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?

States a specific verb and resource ('Create a new support ticket') and enumerates the key fields (title, description, priority, platform). It does not differentiate itself from siblings like update_ticket or fetch_open_tickets, but the core purpose is unambiguous.

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?

The 'When to use' section gives explicit routing: 'Search fetch_documentation first; only open a ticket if docs do not solve the question.' It also specifies when to set assign_to and how to handle ambiguous names. It stops short of naming other ticket tools to prefer, but the trigger condition is clear.

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

All Sweeppea MCP toolsInspect
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.

Resources