add_feedback
ChatGPTCreate a new manual feedback item in a project. Use when creating feedback from scratch with project_id and description. Supports optional title/type/assignee/priority/due date. Write clear, descriptive feedback so teammates can act on it.
get_feedback
ChatGPTLoad full details for known feedback IDs, including screenshot urls and comments. Do not use as a search tool, and do not call it for every search result. Use search tools for lists and call get_feedback only for selected IDs. Use get_feedback_logs when you only need technical console/network diagnostics. Render one section per feedback with key fields, short summary, and notable comments. Always include feedback_app_url for each feedback item so clients can deep-link directly.For multiple feedback items, include a compact overview first, then detailed sections.
get_feedback_logs
ChatGPTRetrieve the most recent console and network log entries for a specific feedback item. Does not support pagination. Use for troubleshooting a specific feedback. Use get_feedback for screenshots, comments, and general feedback details. Returns newest entries first for both console_logs and network_logs. Use limit to cap results per log type; defaults to 20 and maxes at 100.
list_account_users
ChatGPTList account members, optionally scoped to a project and optionally filtered to assignable members. Use to discover user IDs, roles, and names before assigning feedback. Optionally set project_id to return only members with specific project access. Optionally set assignable_only=true to filter to assignable roles.
list_projects
ChatGPTList accessible projects. When to use: discover accessible projects or fetch workflow mappings for UI choices. Set include_workflows=true when workflow names or IDs may be needed next, avoiding extra list_workflows calls per project. Do not call before every search; search tools already enforce project access.
list_workflows
ChatGPTOptional discovery helper: list workflow states for one project in sort order. Workflows are project-scoped; no global states exist. Use when explicitly enumerating states for UI selection. Workflow names and IDs are only valid within the given project_id. Do not call as a preflight on every request - to update the workflow status for a feedback item call set_feedback_workflow with workflow_name or workflow_id.
search_feedback_filter
ChatGPTDeterministic feedback search with structured filters, substring exact matching, sorting, counts, and pagination. Search choice for lists, totals, broad retrieval, or ambiguous tool choice. Use this tool when reproducible coverage and page-by-page control are needed. The search argument is one exact substring matched against title/description, not AND/OR syntax. Use search_feedback_semantic for intent or meaning searches. Start with a small limit and first page, summarize count, then ask before iterating additional pages. Do not auto-loop pages to exhaustion unless the user explicitly requests full export, bulk retrieval, or all feedback. Avoid first-call all-project scans with max limits when a narrower first pass can validate intent. Do not call get_feedback after searching unless selected items need details not returned by search. Issue type is provided as feedback_type (bug, idea, feedback). Render filtered results with a compact summary of count, filters, and sort followed by item sections. When referencing returned feedback, include feedback_app_url so clients can deep-link to the item.
search_feedback_semantic
ChatGPTSemantic relevance retrieval using vector search. Use for meaning-based discovery when exact keywords or filters are unknown and ranking by relevance is desired. Results are relevance-ranked and may be non-exhaustive. Use search_feedback_filter for deterministic filters, counts, paging, stable ordering, or exhaustive coverage. Keep query specific enough to avoid broad noisy matches. One topic per search. Keep the search query simple, do not overexpand and complicate the query. Start with a smaller limit, inspect top matches, then refine the query or confirm expansion. Do not set min_score unless specifically requested. Do not treat semantic output as complete inventory unless the user explicitly accepts approximate ranked retrieval. If you already have IDs, use get_feedback directly instead of searching again. Do not call get_feedback after searching unless selected items need details not returned by search. Render results grouped by best matches first with concise rationale per item, and include feedback_app_url.
set_feedback_assignee
ChatGPTAssign or unassign a known feedback item to a project member. Use list_account_users first when valid user IDs are needed. Set assignee_user_id to 0 to unassign.
set_feedback_workflow
ChatGPTSet feedback workflow by workflow_id or exact workflow_name within the feedback project. Workflow names and IDs are strictly project-scoped. For most status updates where workflow id or name is known within a project, call this directly without list_workflows preflight.
update_feedback
ChatGPTUpdate one or more mutable feedback fields in a single call. Provide at least one update field. For assignee-only changes, prefer set_feedback_assignee. For workflow-only changes, prefer set_feedback_workflow.
add_feedback
Claudeget_feedback
Claudeget_feedback_logs
Claudelist_account_users
Claudelist_projects
Claudelist_workflows
Claudesearch_feedback_filter
Claudesearch_feedback_semantic
Claudeset_feedback_assignee
Claudeset_feedback_workflow
Claudeupdate_feedback
Claude
