Toolbar
Review feedback on your deployments through Vercel Toolbar comment threads. You can reply to messages, edit comments, add reactions, and resolve threads when you address the feedback.
Add an emoji reaction to a message in a toolbar thread.
| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
threadId | string | Yes | - | The thread ID containing the message |
messageId | string | Yes | - | The message ID to react to |
teamId | string | Yes | - | The team ID that owns the thread. Alternatively the team slug can be used. Team IDs start with 'team_'. Can be found by reading .vercel/project.json (orgId) or using list_teams. |
emoji | string | Yes | - | The emoji to add as a reaction (e.g. 👍) |
Sample prompt: "Add a 👍 reaction to message msg_456 on toolbar thread tbt_123"
Change the resolve status of a toolbar thread. Use this to mark a thread as resolved or unresolve a previously resolved thread.
| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
threadId | string | Yes | - | The thread ID to update |
teamId | string | Yes | - | The team ID that owns the thread. Alternatively the team slug can be used. Team IDs start with 'team_'. Can be found by reading .vercel/project.json (orgId) or using list_teams. |
resolved | boolean | Yes | - | Set to true to resolve the thread, false to unresolve it |
Sample prompt: "Mark toolbar thread tbt_123 as resolved"
Edit an existing message in a toolbar thread.
| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
threadId | string | Yes | - | The thread ID containing the message |
messageId | string | Yes | - | The message ID to edit |
teamId | string | Yes | - | The team ID that owns the thread. Alternatively the team slug can be used. Team IDs start with 'team_'. Can be found by reading .vercel/project.json (orgId) or using list_teams. |
markdown | string | Yes | - | The updated message content in markdown format |
Sample prompt: "Update my last toolbar message to clarify the fix"
Get a specific toolbar thread by ID, including all messages and context.
| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
threadId | string | Yes | - | The thread ID to retrieve |
teamId | string | Yes | - | The team ID that owns the thread. Alternatively the team slug can be used. Team IDs start with 'team_'. Can be found by reading .vercel/project.json (orgId) or using list_teams. |
Sample prompt: "Show me the full conversation on toolbar thread tbt_123"
List Vercel Toolbar comment threads for a team. Returns unresolved threads by default.
| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
teamId | string | Yes | - | The team ID to list threads for. Alternatively the team slug can be used. Team IDs start with 'team_'. Can be found by reading .vercel/project.json (orgId) or using the list_teams tool. |
projectId | string | No | - | Filter by project ID |
branch | string | No | - | Filter by branch name |
status | string | No | unresolved | Filter by status: resolved or unresolved |
page | string | No | - | Filter by page path (e.g. /docs) or glob (e.g. /docs*) |
search | string | No | - | Search text in comments |
limit | number | No | 20 | Maximum number of results to return |
offset | number | No | - | Pagination offset |
Sample prompt: "Show me unresolved toolbar comments on my blog project"
Add a reply message to an existing toolbar thread.
| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
threadId | string | Yes | - | The thread ID to reply to |
teamId | string | Yes | - | The team ID that owns the thread. Alternatively the team slug can be used. Team IDs start with 'team_'. Can be found by reading .vercel/project.json (orgId) or using list_teams. |
markdown | string | Yes | - | The message content in markdown format |
Sample prompt: "Reply to toolbar thread tbt_123 with 'Fixed in the latest deploy'"
Was this helpful?