report_issue

Arguments

Argument	Required	Type	Description
`summary`	Yes	string, up to 200 characters	One sentence saying what happened, 10 to 200 characters.
`category`	Yes	one of: `slow`, `error`, `confusing`, `workaround`, `wrong_result`, `missing_capability`, `worked_well`, `other`	slow: a tool or job took too long. error: an error you didn’t expect, or one that didn’t say how to fix it. confusing: a description, input or answer that was unclear. workaround: you had to work around a design, with extra calls, guessing or retrying. wrong_result: a result was wrong. missing_capability: Pomerado can’t do something you needed. worked_well: something worked notably well. other: anything else.
`task_outcome`	Yes	one of: `completed`, `completed_with_workaround`, `partially_completed`, `blocked`	How your task ended: completed, completed_with_workaround, partially_completed or blocked.
`details`	No	string, up to 4,000 characters	What you tried and what happened, up to 4,000 characters, quoting exact tool names, error codes and parameter names.
`suggested_improvement`	No	string, up to 1,000 characters	The one change that would have helped, up to 1,000 characters.
`waited_seconds`	No	integer, 0 to 86400	For slow: about how many seconds it took, 0 to 86,400.
`related`	No	object	What the report is about. Pomerado links only the IDs you can read.

Output

The stored report: its report_id, whether it was recorded or merged with the same report you sent within a day, its severity, the related IDs Pomerado linked, and a message saying to carry on with the task.

{
  "summary": "run_website_tool waited 90 seconds before answering a simple search.",
  "category": "slow",
  "task_outcome": "completed",
  "details": "Searched flights with run_read_only_website_tool; the job stayed running for 90 seconds, then succeeded.",
  "waited_seconds": 90,
  "related": { "job_id": "job_dddddddddddddddddddddddddddddddd" }
}

{
  "report_id": "rpt_eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee",
  "status": "recorded",
  "severity": "low",
  "linked": {
    "job_id": "job_dddddddddddddddddddddddddddddddd",
    "tool_id": null,
    "integration_id": null
  },
  "message": "Thanks, the Pomerado team will read this. Carry on with your task."
}

Details

Report friction when it happens, once per problem: a tool or job that was slow, a description, input or answer that was confusing, an error you didn’t expect or that didn’t say how to fix it, a wrong result, or a design you had to work around (extra calls, guessing, retrying). You may also say when something worked notably well. Don’t report the user’s own mistakes (a wrong input, a missing login, a refused permission) or website problems Pomerado explained clearly. If one tool lacks a filter, input or output, use change_website_tool instead. Write a one-sentence summary. In details, say what you tried and what happened, quoting exact tool names, error codes and parameter names. Never include passwords, codes, tokens, card numbers, personal details, page content or the user’s data; describe them generally (“the order number field”). Pass the job_id or tool you used; Pomerado attaches the rest. This is a side report: after it answers, carry on with the user’s task. Don’t retry it if it’s refused. Its answer says where the user can get help faster, such as the user emailing founders@pomerado.ai when it’s urgent. You may pass that on, but ask the user before sending any email; never email on your own.Effect: May change a website or your account.

Overview

Pomerado MCP

Integration MCP

Arguments

Output

​Arguments

​Output

Arguments

Output