MCP tools reference
The four tools the PinMarks MCP server exposes, with their parameters.
Updated October 2026
What the assistant can see
It acts as you, with access to every project in every workspace you belong to. It can read feedback and change a status; it cannot create issues, comment or assign.
list_projects
No parameters. Returns each project's id, name, domain and workspace id.
list_feedback
| Parameter | Description |
|---|---|
project_id | Optional project id. |
status | open, in_progress, resolved, closed, wont_fix or waiting_for_approval. |
type | bug, suggestion, question or other. |
priority | low, medium, high or critical. |
search | Text to match in title and description (max 100 characters). |
limit / offset | Page size 1 to 50 (default 20) and starting position. |
Returns the total and the newest matching issues, with descriptions shortened to 300 characters.
get_feedback
Takes feedback_id and optionally include_screenshot (default true). Returns the full issue: title, description, type, status, priority, page URL, reporter, assignee, browser and device details, up to 50 console logs (errors first), up to 30 failed network requests, custom metadata, tracker link, up to 30 comments and the screenshot as an image.
update_feedback_status
Takes feedback_id and status. It behaves like changing the status in the dashboard: the linked tracker issue is updated and your team is notified.
Example prompts
- "List the open critical bugs in my Acme website project."
- "Read feedback <id>, find the cause in this repo and suggest a fix."
- "Mark feedback <id> as resolved."
Still stuck?
Email support@pinmarks.io and we'll get back to you within one business day.