Permissions and results
Every tool requires the listed scope as well as current organisation owner/admin access and active billing. add_comment additionally requires the workspace owner. Write scopes do not imply read scopes. Unknown schema properties are rejected; all IDs and related feedback are workspace-scoped. Success contains structuredContent and matching JSON text in content. Authorised revenue amounts are integer cents; results exclude raw customer emails and raw associations.
| Tool | Scope | Arguments and behavior |
|---|---|---|
get_workspace | feedback:read | No arguments; workspace, board URL, statuses, roadmap columns, connected apps and revenue-weighting state. |
list_feedback | feedback:read | Optional status, connected_app_id, sort and limit. Limit 1–100, default 25. Sort defaults to revenue; also cancelled, top, newest, recently_active. Status accepts open, planned, in_progress, shipped, archived; archived items require explicit status=archived. |
search_feedback | feedback:read | Required query 1–200 characters; limit 1–25, default 10. Search before creating. |
get_feedback | feedback:read | Exactly one of id (UUID) or slug (at most 255 characters), enforced at runtime; detail, sources, comments and aggregate revenue. |
create_feedback | feedback:write | Required title; optional description (at most 10,000 characters) and connected_app_id. Creates open feedback. |
update_feedback | feedback:write | Required id and at least one of status, title, description or roadmap_column; optional note. Status open/planned/in_progress/shipped; column now/next/later. Description at most 10,000 characters. |
add_comment | feedback:write | Required id, body 1–10,000 characters and explicit public boolean. Workspace owner only. |
merge_feedback | feedback:write | Distinct source_id and target_id; moves votes to target and archives source. Destructive; no UI undo. |
list_changelog | changelog:read | Optional status draft/published; limit 1–50, default 20. Published entries first by publication time descending, drafts last, then updated time descending. Use status=draft to find recent drafts: published entries can fill the default limit. Public URLs only for published entries. |
create_changelog_draft | changelog:write | Required title and Markdown body 1–50,000 characters; related_feedback_ids at most 20, all in this workspace, deduplicated. Draft only. |
Read feedback
Call get_workspace first to discover the connected workspace and apps. Use revenue ranking to understand paying voters, or cancelled to rank by lost revenue. Search before creating duplicates. The get_feedback schema does not declare id or slug required, but runtime validation requires exactly one, not both.
Write feedback
Schema limits and domain limits both apply. Feedback title schemas accept 1–200 characters, but the domain requires 3–160. The update note schema allows 1,000 characters, but the domain requires a single line of at most 280 characters. Notes record why a status changed and may appear in shipped-update emails: do not put confidential information in them.
For add_comment, public=true is visible to customers on the public board; public=false keeps the comment internal. An admin write grant does not bypass this owner-only restriction.
Changelog tools
The changelog title schema accepts 1–200 characters, but domain validation allows at most 140. create_changelog_draft creates a draft only; it cannot publish. A person reviews and publishes in Upweight. There is no changelog publication or deletion tool. See publishing a changelog.
Confirm consequential actions
Obtain confirmation before shipping, merging or posting public comments. Setting status to shipped can email opted-in voters through shipped-update emails; delivery depends on eligibility and configuration. Do not rely on client annotations to guarantee a confirmation prompt. Status history records the authenticated user and optional note.
Merging is destructive with no UI undo. Confirm the intended source and target before calling it. Other writes also have real effects, not simulated ones. Validation failures return readable tool errors; they are not permission to bypass domain rules. See error distinctions.