Prompt: Lista los issues abiertos de 'data-pipeline' con label 'enhancement'.

Add review comment to the requester's latest pending pull request review. A pending review needs to already exist to call this (check with the user if not sure).

The text of the review comment

The line of the blob in the pull request diff that the comment applies to. For multi-line comments, the last line of the range

Repository owner

The relative path to the file that necessitates a comment

Pull request number

Repository name

The side of the diff to comment on. LEFT indicates the previous state, RIGHT indicates the new state

For multi-line comments, the first line of the range that the comment applies to

For multi-line comments, the starting side of the diff that the comment applies to

The level at which the comment is targeted

Add a comment to a specific issue in a GitHub repository. Use this tool to add comments to pull requests as well (in this case pass pull request number as issue_number), but only if user is not asking specifically to add review comments.

Comment content

Issue number to comment on

Repository owner

Repository name

Add a reply to an existing pull request comment. This creates a new comment that is linked as a reply to the specified comment.

The text of the reply

The ID of the comment to reply to

Repository owner

Pull request number

Repository name

Assign Copilot to a specific issue in a GitHub repository.

This tool can help with the following outcomes:
- a Pull Request created with source code changes to resolve the issue

More information can be found at:
- https://docs.github.com/en/copilot/using-github-copilot/using-copilot-coding-agent-to-work-on-tasks/about-assigning-tasks-to-copilot

Git reference (e.g., branch) that the agent will start its work from. If not specified, defaults to the repository's default branch

Optional custom instructions to guide the agent beyond the issue body.

Issue number

Repository owner

Repository name

Create a new branch in a GitHub repository

Name for new branch

Source branch (defaults to repo default)

Repository owner

Repository name

Create or update a single file in a GitHub repository.
If updating, you should provide the SHA of the file you want to update. Use this tool to create or update a file in a GitHub repository remotely; do not use it for local file operations.

In order to obtain the SHA of original file version before updating, use the following git command:
git rev-parse <branch>:<path to file>

SHA MUST be provided for existing file updates.

Branch to create/update the file in

Content of the file

Commit message

Repository owner (username or organization)

Path where to create/update the file

Repository name

The blob SHA of the file being replaced. Required if the file already exists.

Create a new pull request in a GitHub repository.

Branch to merge into

PR description

Create as draft PR

Branch containing changes

Allow maintainer edits

Repository owner

Repository name

PR title

Create a new GitHub repository in your account or specified organization

Initialize with README

Repository description

Repository name

Organization to create the repository in (omit to create in your personal account)

Whether repo should be private

Delete a file from a GitHub repository

Branch to delete the file from

Commit message

Path to the file to delete

Repository name

Fork a GitHub repository to your account or specified organization

Organization to fork to

Repository owner

Repository name

Get details for a commit from a GitHub repository

Whether to include file diffs and stats in the response. Default is true.

Repository owner

Page number for pagination (min 1)

Results per page for pagination (min 1, max 100)

Repository name

Commit SHA, branch name, or tag name

Get the contents of a file or directory from a GitHub repository

Path to file/directory

Accepts optional git refs such as `refs/tags/{tag}`, `refs/heads/{branch}` or `refs/pull/{pr_number}/head`

Repository name

Accepts optional commit SHA. If specified, it will be used instead of ref

Get a specific label from a repository.

Label name.

Repository owner (username or organization name)

Repository name

Get the latest release in a GitHub repository

Repository owner

Repository name

Get details of the authenticated GitHub user. Use this when a request is about the user's own profile for GitHub. Or when information is missing to build other tool calls.

Get a specific release by its tag name in a GitHub repository

Repository owner

Repository name

Tag name (e.g., 'v1.0.0')

Get details about a specific git tag in a GitHub repository

Repository owner

Repository name

Tag name

Get member usernames of a specific team in an organization. Limited to organizations accessible with current credentials

Organization login (owner) that contains the team.

Team slug

Get details of the teams the user is a member of. Limited to organizations accessible with current credentials

Username to get teams for. If not provided, uses the authenticated user.

Get information about a specific issue in a GitHub repository.

The number of the issue

1. get - Get details of a specific issue. 2. get_comments - Get issue comments. 3. get_sub_issues - Get sub-issues of the issue. 4. get_labels - Get labels assigned to the issue.

The owner of the repository

Page number for pagination (min 1)

The name of the repository

Create a new or update an existing issue in a GitHub repository.

Usernames to assign to this issue

Issue body content

Issue number that this issue is a duplicate of. Only used when state_reason is 'duplicate'.

Issue number to update

Labels to apply to this issue

'create' creates a new issue. 'update' updates an existing issue.

Milestone number

Repository owner

Repository name

New state

Reason for the state change. Ignored unless state is changed.

Issue title

Type of this issue. Only use if the repository has issue types configured.

List branches in a GitHub repository

Repository owner

Page number for pagination (min 1)

Results per page for pagination (min 1, max 100)

Repository name

Get list of commits of a branch in a GitHub repository. Returns at least 30 results per page by default, but can return more if specified using the perPage parameter (up to 100).

Author username or email address to filter commits by

Repository owner

Page number for pagination (min 1)

Only commits containing this file path will be returned

Repository name

Commit SHA, branch or tag name to list commits of. Defaults to the default branch.

Only commits after this date (ISO 8601)

Only commits before this date (ISO 8601)

List supported issue types for repository owner (organization).

The organization owner of the repository

List issues in a GitHub repository. For pagination, use the 'endCursor' from the previous response's 'pageInfo' in the 'after' parameter.

Cursor for pagination.

Order direction. Requires 'orderBy' too.

Filter by labels

Order issues by field. Requires 'direction' too.

Repository owner

Repository name

Filter by date (ISO 8601 timestamp)

Filter by state

List pull requests in a GitHub repository. If the user specifies an author, then DO NOT use this tool and use the search_pull_requests tool instead.

Filter by base branch

Sort direction

Filter by head user/org and branch

Repository owner

Page number for pagination (min 1)

Repository name

Sort by

Filter by state

List releases in a GitHub repository

Repository owner

Page number for pagination (min 1)

Repository name

List collaborators of a GitHub repository. Results are paginated; the response includes `nextPage`, `prevPage`, `firstPage`, and `lastPage` fields. To get the next page, use the `nextPage` value as the `page` parameter.

Filter by affiliation. Default: 'all'

Repository owner

Page number for pagination (default 1, min 1)

Results per page for pagination (default 30, min 1, max 100)

Repository name

List git tags in a GitHub repository

Repository owner

Page number for pagination (min 1)

Repository name

Merge a pull request in a GitHub repository.

Extra detail for merge commit

Title for merge commit

Merge method

Repository owner

Pull request number

Repository name

Get information on a specific pull request in GitHub repository.

Cursor for pagination, used only by get_review_comments.

1. get 2. get_diff 3. get_status 4. get_files 5. get_review_comments 6. get_reviews 7. get_comments 8. get_check_runs

Repository owner

Page number for pagination (min 1)

Results per page for pagination (min 1, max 100)

Pull request number

Repository name

Create and/or submit, delete review of a pull request.

- create: Create a new review of a pull request. If "event" is provided, the review is submitted; if omitted, a pending review is created.
- submit_pending: Submit an existing pending review.
- delete_pending: Delete an existing pending review.
- resolve_thread / unresolve_thread: only need "threadId".

Review comment text

SHA of commit to review

Review action to perform.

Repository owner

Pull request number

Repository name

Node ID of the review thread (e.g., PRRT_kwDOxxx). Required for resolve/unresolve_thread.

Push multiple files to a GitHub repository in a single commit

Branch to push to

Array of file objects to push, each object with path (string) and content (string)

file content

path to the file

Commit message

Repository owner

Repository name

Request a GitHub Copilot code review for a pull request. Use this for automated feedback on pull requests, usually before requesting a human reviewer.

Repository owner

Pull request number

Repository name

Fast and precise code search across ALL GitHub repositories using GitHub's native search engine. Best for finding exact symbols, functions, classes, or specific code patterns.

Sort order for results

Page number for pagination (min 1)

Search query (GitHub code search REST). Supports OR/NOT/quoted phrases and qualifiers repo:/org:/user:/language:/path:/filename:/extension:/in:file/in:path/size:/is:archived/is:fork. Max 256 chars.

Sort field ('indexed' only)

Search for commits across GitHub repositories using GitHub's commit search syntax. Searches the default branch only.

Sort order

Page number for pagination (min 1)

Commit search query. Scope with repo:/org:/user:. Other qualifiers: author:, committer:, author-date:, merge:, hash:, tree:, parent:, is:public.

Sort by author or committer date (defaults to best match)

Search for issues in GitHub repositories using issues search syntax already scoped to is:issue

Sort order

Optional repository owner. If provided with repo, only issues for this repository are listed.

Page number for pagination (min 1)

Search query using GitHub issues search syntax

Optional repository name. If provided with owner, only issues for this repository are listed.

Sort field by number of matches of categories, defaults to best match

Search for pull requests in GitHub repositories using issues search syntax already scoped to is:pr

Sort order

Optional repository owner. If provided with repo, only pull requests for this repository are listed.

Page number for pagination (min 1)

Search query using GitHub pull request search syntax

Optional repository name. If provided with owner, only pull requests for this repository are listed.

Find GitHub repositories by name, description, readme, topics, or other metadata. Perfect for discovering projects, finding examples, or locating specific repositories across GitHub.

Return minimal repository information (default: true). When false, returns full GitHub API repository objects.

Sort order

Page number for pagination (min 1)

Results per page for pagination (min 1, max 100)

Repository search query. Examples: 'machine learning in:name stars:>1000 language:python', 'topic:react', 'user:facebook'.

Sort repositories by field, defaults to best match

Find GitHub users by username, real name, or other profile information. Useful for locating developers, contributors, or team members.

Sort order

Page number for pagination (min 1)

User search query. Examples: 'john smith', 'location:seattle', 'followers:>100'. Search is automatically scoped to type:user.

Sort users by number of followers or repositories, or when the person joined GitHub.

Update an existing pull request in a GitHub repository.

New base branch name

New description

Mark pull request as draft (true) or ready for review (false)

Allow maintainer edits

Repository owner

Pull request number to update

Repository name

GitHub usernames to request reviews from

New state

New title

Update the branch of a pull request with the latest changes from the base branch.

The expected SHA of the pull request's HEAD ref

Repository owner

Pull request number

Repository name

Add a sub-issue to a parent issue in a GitHub repository.

The ID of the sub-issue to be prioritized after (either after_id OR before_id should be specified)

The ID of the sub-issue to be prioritized before (either after_id OR before_id should be specified)

The number of the parent issue

'add' - add a sub-issue to a parent issue. 'remove' - remove a sub-issue from a parent issue. 'reprioritize' - change the order of sub-issues within a parent issue, using 'after_id' or 'before_id'.

Repository owner

When true, replaces the sub-issue's current parent issue. Use with 'add' method only.

Repository name

The ID of the sub-issue to add. ID is not the same as issue number


Prompt: Lista los releases publicados de 'mobile-client'.

Add review comment to the requester's latest pending pull request review. A pending review needs to already exist to call this (check with the user if not sure).

The text of the review comment

The line of the blob in the pull request diff that the comment applies to. For multi-line comments, the last line of the range

Repository owner

The relative path to the file that necessitates a comment

Pull request number

Repository name

The side of the diff to comment on. LEFT indicates the previous state, RIGHT indicates the new state

For multi-line comments, the first line of the range that the comment applies to

For multi-line comments, the starting side of the diff that the comment applies to

The level at which the comment is targeted

owner repo pullNumber path body subjectType

Add a comment to a specific issue in a GitHub repository. Use this tool to add comments to pull requests as well (in this case pass pull request number as issue_number), but only if user is not asking specifically to add review comments.

Comment content

Issue number to comment on

Repository owner

Repository name

Add a reply to an existing pull request comment. This creates a new comment that is linked as a reply to the specified comment.

The text of the reply

The ID of the comment to reply to

Repository owner

Pull request number

Repository name

Assign Copilot to a specific issue in a GitHub repository.

This tool can help with the following outcomes:
- a Pull Request created with source code changes to resolve the issue

More information can be found at:
- https://docs.github.com/en/copilot/using-github-copilot/using-copilot-coding-agent-to-work-on-tasks/about-assigning-tasks-to-copilot

Git reference (e.g., branch) that the agent will start its work from. If not specified, defaults to the repository's default branch

Optional custom instructions to guide the agent beyond the issue body.

Issue number

Repository owner

Repository name

Create a new branch in a GitHub repository

Name for new branch

Source branch (defaults to repo default)

Repository owner

Repository name

Create or update a single file in a GitHub repository.
If updating, you should provide the SHA of the file you want to update. Use this tool to create or update a file in a GitHub repository remotely; do not use it for local file operations.

In order to obtain the SHA of original file version before updating, use the following git command:
git rev-parse <branch>:<path to file>

SHA MUST be provided for existing file updates.

Branch to create/update the file in

Content of the file

Commit message

Repository owner (username or organization)

Path where to create/update the file

Repository name

The blob SHA of the file being replaced. Required if the file already exists.

Create a new pull request in a GitHub repository.

Branch to merge into

PR description

Create as draft PR

Branch containing changes

Allow maintainer edits

Repository owner

Repository name

PR title

Create a new GitHub repository in your account or specified organization

Initialize with README

Repository description

Repository name

Organization to create the repository in (omit to create in your personal account)

Whether repo should be private

Delete a file from a GitHub repository

Branch to delete the file from

Commit message

Path to the file to delete

Repository name

Fork a GitHub repository to your account or specified organization

Organization to fork to

Repository owner

Repository name

Get details for a commit from a GitHub repository

Whether to include file diffs and stats in the response. Default is true.

Repository owner

Page number for pagination (min 1)

Results per page for pagination (min 1, max 100)

Repository name

Commit SHA, branch name, or tag name

Get the contents of a file or directory from a GitHub repository

Path to file/directory

Accepts optional git refs such as `refs/tags/{tag}`, `refs/heads/{branch}` or `refs/pull/{pr_number}/head`

Repository name

Accepts optional commit SHA. If specified, it will be used instead of ref

Get a specific label from a repository.

Label name.

Repository owner (username or organization name)

Repository name

Get the latest release in a GitHub repository

Repository owner

Repository name

Get details of the authenticated GitHub user. Use this when a request is about the user's own profile for GitHub. Or when information is missing to build other tool calls.

Get a specific release by its tag name in a GitHub repository

Repository owner

Repository name

Tag name (e.g., 'v1.0.0')

Get details about a specific git tag in a GitHub repository

Repository owner

Repository name

Tag name

Get member usernames of a specific team in an organization. Limited to organizations accessible with current credentials

Organization login (owner) that contains the team.

Team slug

Get details of the teams the user is a member of. Limited to organizations accessible with current credentials

Username to get teams for. If not provided, uses the authenticated user.

Get information about a specific issue in a GitHub repository.

The number of the issue

1. get - Get details of a specific issue. 2. get_comments - Get issue comments. 3. get_sub_issues - Get sub-issues of the issue. 4. get_labels - Get labels assigned to the issue.

The owner of the repository

Page number for pagination (min 1)

The name of the repository

Create a new or update an existing issue in a GitHub repository.

Usernames to assign to this issue

Issue body content

Issue number that this issue is a duplicate of. Only used when state_reason is 'duplicate'.

Issue number to update

Labels to apply to this issue

'create' creates a new issue. 'update' updates an existing issue.

Milestone number

Repository owner

Repository name

New state

Reason for the state change. Ignored unless state is changed.

Issue title

Type of this issue. Only use if the repository has issue types configured.

List branches in a GitHub repository

Repository owner

Page number for pagination (min 1)

Results per page for pagination (min 1, max 100)

Repository name

Get list of commits of a branch in a GitHub repository. Returns at least 30 results per page by default, but can return more if specified using the perPage parameter (up to 100).

Author username or email address to filter commits by

Repository owner

Page number for pagination (min 1)

Only commits containing this file path will be returned

Repository name

Commit SHA, branch or tag name to list commits of. Defaults to the default branch.

Only commits after this date (ISO 8601)

Only commits before this date (ISO 8601)

List supported issue types for repository owner (organization).

The organization owner of the repository

List issues in a GitHub repository. For pagination, use the 'endCursor' from the previous response's 'pageInfo' in the 'after' parameter.

Cursor for pagination.

Order direction. Requires 'orderBy' too.

Filter by labels

Order issues by field. Requires 'direction' too.

Repository owner

Repository name

Filter by date (ISO 8601 timestamp)

Filter by state

List pull requests in a GitHub repository. If the user specifies an author, then DO NOT use this tool and use the search_pull_requests tool instead.

Filter by base branch

Sort direction

Filter by head user/org and branch

Repository owner

Page number for pagination (min 1)

Repository name

Sort by

Filter by state

List releases in a GitHub repository

Repository owner

Page number for pagination (min 1)

Repository name

List collaborators of a GitHub repository. Results are paginated; the response includes `nextPage`, `prevPage`, `firstPage`, and `lastPage` fields. To get the next page, use the `nextPage` value as the `page` parameter.

Filter by affiliation. Default: 'all'

Repository owner

Page number for pagination (default 1, min 1)

Results per page for pagination (default 30, min 1, max 100)

Repository name

List git tags in a GitHub repository

Repository owner

Page number for pagination (min 1)

Repository name

Merge a pull request in a GitHub repository.

Extra detail for merge commit

Title for merge commit

Merge method

Repository owner

Pull request number

Repository name

Get information on a specific pull request in GitHub repository.

Cursor for pagination, used only by get_review_comments.

1. get 2. get_diff 3. get_status 4. get_files 5. get_review_comments 6. get_reviews 7. get_comments 8. get_check_runs

Repository owner

Page number for pagination (min 1)

Results per page for pagination (min 1, max 100)

Pull request number

Repository name

Create and/or submit, delete review of a pull request.

- create: Create a new review of a pull request. If "event" is provided, the review is submitted; if omitted, a pending review is created.
- submit_pending: Submit an existing pending review.
- delete_pending: Delete an existing pending review.
- resolve_thread / unresolve_thread: only need "threadId".

Review comment text

SHA of commit to review

Review action to perform.

Repository owner

Pull request number

Repository name

Node ID of the review thread (e.g., PRRT_kwDOxxx). Required for resolve/unresolve_thread.

Push multiple files to a GitHub repository in a single commit

Branch to push to

Array of file objects to push, each object with path (string) and content (string)

file content

path to the file

Commit message

Repository owner

Repository name

Request a GitHub Copilot code review for a pull request. Use this for automated feedback on pull requests, usually before requesting a human reviewer.

Repository owner

Pull request number

Repository name

Fast and precise code search across ALL GitHub repositories using GitHub's native search engine. Best for finding exact symbols, functions, classes, or specific code patterns.

Sort order for results

Page number for pagination (min 1)

Search query (GitHub code search REST). Supports OR/NOT/quoted phrases and qualifiers repo:/org:/user:/language:/path:/filename:/extension:/in:file/in:path/size:/is:archived/is:fork. Max 256 chars.

Sort field ('indexed' only)

Search for commits across GitHub repositories using GitHub's commit search syntax. Searches the default branch only.

Sort order

Page number for pagination (min 1)

Commit search query. Scope with repo:/org:/user:. Other qualifiers: author:, committer:, author-date:, merge:, hash:, tree:, parent:, is:public.

Sort by author or committer date (defaults to best match)

Search for issues in GitHub repositories using issues search syntax already scoped to is:issue

Sort order

Optional repository owner. If provided with repo, only issues for this repository are listed.

Page number for pagination (min 1)

Search query using GitHub issues search syntax

Optional repository name. If provided with owner, only issues for this repository are listed.

comments reactions reactions-+1 reactions--1 reactions-smile reactions-thinking_face reactions-heart reactions-tada interactions created updated

Sort field by number of matches of categories, defaults to best match

Search for pull requests in GitHub repositories using issues search syntax already scoped to is:pr

Sort order

Optional repository owner. If provided with repo, only pull requests for this repository are listed.

Page number for pagination (min 1)

Search query using GitHub pull request search syntax

Optional repository name. If provided with owner, only pull requests for this repository are listed.

Find GitHub repositories by name, description, readme, topics, or other metadata. Perfect for discovering projects, finding examples, or locating specific repositories across GitHub.

Return minimal repository information (default: true). When false, returns full GitHub API repository objects.

Sort order

Page number for pagination (min 1)

Results per page for pagination (min 1, max 100)

Repository search query. Examples: 'machine learning in:name stars:>1000 language:python', 'topic:react', 'user:facebook'.

Sort repositories by field, defaults to best match

Find GitHub users by username, real name, or other profile information. Useful for locating developers, contributors, or team members.

Sort order

Page number for pagination (min 1)

User search query. Examples: 'john smith', 'location:seattle', 'followers:>100'. Search is automatically scoped to type:user.

Sort users by number of followers or repositories, or when the person joined GitHub.

Update an existing pull request in a GitHub repository.

New base branch name

New description

Mark pull request as draft (true) or ready for review (false)

Allow maintainer edits

Repository owner

Pull request number to update

Repository name

GitHub usernames to request reviews from

New state

New title

Update the branch of a pull request with the latest changes from the base branch.

The expected SHA of the pull request's HEAD ref

Repository owner

Pull request number

Repository name

Add a sub-issue to a parent issue in a GitHub repository.

The ID of the sub-issue to be prioritized after (either after_id OR before_id should be specified)

The ID of the sub-issue to be prioritized before (either after_id OR before_id should be specified)

The number of the parent issue

'add' - add a sub-issue to a parent issue. 'remove' - remove a sub-issue from a parent issue. 'reprioritize' - change the order of sub-issues within a parent issue, using 'after_id' or 'before_id'.

Repository owner

When true, replaces the sub-issue's current parent issue. Use with 'add' method only.

Repository name

The ID of the sub-issue to add. ID is not the same as issue number


Prompt: Comenta 'tabla de precios 284' en la pagina con id conocido del space 'data-pipeline'.

Check for new comments across pages in a space since a given timestamp. Optionally scope to a page subtree (folder). Returns only comments created after the specified time.

Space ID to check for new comments

ISO 8601 timestamp — only return comments created after this time (e.g. '2026-03-10T00:00:00Z')

Optional root page ID to scope the check to a subtree (folder). Only pages under this parent will be checked.

Create a new comment on a page. Content is provided as Markdown and automatically converted to the required format.

ID of the page to comment on

Comment content in Markdown format

Parent comment ID to create a reply (max 2 nesting levels)

Selected text for inline comments (max 250 chars). Required when type is 'inline'.

Comment type: 'page' for general page comment (default), 'inline' for text selection comment

Create a new page with content (automatically moves it to the correct hierarchy).

Title of the page

Markdown content

Optional parent page ID to nest under

Delete a comment. Only the comment creator or space admin can delete it.

ID of the comment to delete

Delete a single page by ID.

Delete multiple pages at once. Useful for cleanup.

Get a single comment by ID with content as Markdown.

ID of the comment

Get details and content of a specific page by ID

Get the current Docmost workspace

List all comments on a page. Returns comments with content converted to Markdown.

ID of the page to list comments for

List all available groups in Docmost

List pages in a space ordered by updatedAt (descending).

List all available spaces in Docmost

Move a page to a new parent (nesting) or root. Essential for organizing pages created via 'import_page'.

Target parent page ID. Pass 'null' or empty string to move to root.

Optional position string (5-12 chars). Defaults to 'a00000' (end) if omitted.

search

Search for pages and content.

Search query

Optional space ID to filter by

Update an existing comment's content. Only the comment creator can update it. Content is provided as Markdown.

ID of the comment to update

New comment content in Markdown format

Update a page's content and/or title via realtime collaboration (preserves Page ID and history).

ID of the page to update

New Markdown content

Optional new title

Requiere SIEMPRE la fila separadora GFM (| --- | --- |) en tablas markdown, con cada fila en su propia linea -- sin eso el editor colapsa las filas en un parrafo ilegible (bug real documentado en el plan principal).


Prompt: Mueve la pagina 'bugfix urgente 307' a otro parent dentro del space 'mobile-client'.

Check for new comments across pages in a space since a given timestamp. Optionally scope to a page subtree (folder). Returns only comments created after the specified time.

Space ID to check for new comments

ISO 8601 timestamp — only return comments created after this time (e.g. '2026-03-10T00:00:00Z')

Optional root page ID to scope the check to a subtree (folder). Only pages under this parent will be checked.

Create a new comment on a page. Content is provided as Markdown and automatically converted to the required format.

ID of the page to comment on

Comment content in Markdown format

Parent comment ID to create a reply (max 2 nesting levels)

Selected text for inline comments (max 250 chars). Required when type is 'inline'.

Comment type: 'page' for general page comment (default), 'inline' for text selection comment

Create a new page with content (automatically moves it to the correct hierarchy).

Title of the page

Markdown content

Optional parent page ID to nest under

Delete a comment. Only the comment creator or space admin can delete it.

ID of the comment to delete

Delete a single page by ID.

Delete multiple pages at once. Useful for cleanup.

Get a single comment by ID with content as Markdown.

ID of the comment

Get details and content of a specific page by ID

Get the current Docmost workspace

List all comments on a page. Returns comments with content converted to Markdown.

ID of the page to list comments for

List all available groups in Docmost

List pages in a space ordered by updatedAt (descending).

List all available spaces in Docmost

Move a page to a new parent (nesting) or root. Essential for organizing pages created via 'import_page'.

Target parent page ID. Pass 'null' or empty string to move to root.

Optional position string (5-12 chars). Defaults to 'a00000' (end) if omitted.

Search for pages and content.

Search query

Optional space ID to filter by

Update an existing comment's content. Only the comment creator can update it. Content is provided as Markdown.

ID of the comment to update

New comment content in Markdown format

Update a page's content and/or title via realtime collaboration (preserves Page ID and history).

ID of the page to update

New Markdown content

Optional new title


Prompt: Mergea (solo si el usuario lo pide explicitamente) el PR numero 480 de 'backend-core'.

Read Actions secrets and variables.

for get methods

for org methods

for repo methods

page

results per page

for repo methods

Write Actions secrets and variables: upsert, create, update, delete.

secret value (upsert)

secret or variable name

for org methods

for repo methods

for repo methods

variable value

Read Actions workflows, runs, jobs, and logs.

for log methods

max log bytes

for 'download_job_log'

repo owner

page

results per page

repo name

for 'get_run'/'list_run_jobs'

filter for 'list_runs'/'list_jobs'

log tail lines

ID or filename (for 'get_workflow')

Write Actions runs: dispatch, cancel, rerun.

for 'dispatch_workflow'

repo owner

branch or tag (for 'dispatch_workflow')

repo name

for 'cancel_run'/'rerun_run'

ID or filename (for 'dispatch_workflow')

source branch (default: repo default)

repo owner

repo name

Create or update a file (provide sha to update an existing file).

commit message

new branch (create only)

repo owner

repo name

existing file SHA (omit to create)

owner repo path content message branch_name

repo owner

repo name

commitish

defaults to personal account

default collaborator committer collaboratorcommitter

tag message

repo owner

repo name

commitish

repo owner

repo name

commit message

repo owner

repo name

repo owner

repo name

repo owner

repo name

fork name

target org

owner of source repo

repo owner

repo name

repo owner

branch, tag, or commit SHA

repo name

Get file content and metadata

repo owner

branch, tag, or commit SHA

repo name

return numbered lines

repo owner

repo name

Get current user

Get a release by ID

repo owner

repo name

repo owner

page

results per page

repo name

SHA, branch, or tag

repo owner

repo name

List current user's organizations

page

results per page

Read issue: details, comments, or labels.

repo owner

repo name

Write issues: create, update, manage comments and labels.

required for 'create'/'add_comment'/'edit_comment'

for 'edit_comment'

ISO 8601

required except for 'create'

for 'remove_label'

label IDs

repo owner

branch to associate

repo name

required for 'create'

Read repo or org labels.

label ID (for 'get_repo_label')

for org methods

for repo methods

page

results per page

for repo methods

Write labels (repo or org): create, edit, delete.

hex (#RRGGBB); required for create

exclusive (org only)

for edit/delete

archived (repo only)

required for create

for org methods

for repo methods

for repo methods

repo owner

page

results per page

repo name

repo owner

page

only commits touching this path

results per page

repo name

starting SHA or branch

updated before ISO 8601

label name filter

repo owner

page

results per page

repo name

updated after ISO 8601

page

results per page

page

results per page

repo owner

page

results per page

repo name

oldest recentupdate leastupdate mostcomment leastcomment priority

repo owner

page

results per page

repo name

repo owner

page

results per page

repo name

Read milestones: get one or list.

for 'get'

name filter (for 'list')

repo owner

page

results per page

repo name

Write milestones: create, update, delete.

due date

for 'update'/'delete'

repo owner

repo name

for 'create'

Read notifications: list (optionally scoped to a repo) or get a thread by ID.

updated before ISO 8601

thread ID (for 'get')

scope 'list' to a repo

page

results per page

scope 'list' to a repo

updated after ISO 8601

Mark a notification or all notifications as read.

thread ID (for 'mark_read')

ISO 8601; defaults to now

scope 'mark_all_read' to a repo

scope 'mark_all_read' to a repo

Read package registry: list packages (one entry per version, filter via 'q'/'type'), list versions, or get a version.

slashes auto-encoded; required except 'list'

user or org

page

results per page

search query

container/npm/maven/pypi/cargo/generic; required except 'list'

for 'get'

Delete a package version (irreversible).

slashes auto-encoded

user or org

container/npm/maven/pypi/cargo/generic

Read pull request: details, diff, changed files, head commit status, reviews.

include binary diff

repo owner

page

results per page

repo name

for 'get_review'/'get_review_comments'

Write PR reviews: create, submit, delete, dismiss.

inline comments (for 'create')

new-file line (additions)

old-file line (deletions)

for 'create'

dismissal reason

repo owner

repo name

required except for 'create'

APPROVED REQUEST_CHANGES COMMENT PENDING

Write pull requests: create, update, close, reopen, merge, update branch from base, manage reviewers.

for 'update'

for 'update'

for 'update'

base branch (required for 'create')

ISO 8601

for 'merge'

uses 'WIP: ' title prefix

merge even if checks fail

head branch (required for 'create')

expected head SHA for conflict detection

label IDs

merge rebase rebase-merge squash fast-forward-only

for 'merge'

for 'merge'

merge commit message or dismissal reason

for 'update'

repo owner

required except for 'create'

for 'update'

repo name

for 'add_reviewers'/'remove_reviewers'

for 'update'

for 'add_reviewers'/'remove_reviewers'

required for 'create'; optional for 'update'/'merge'

Search issues and PRs across repositories

comma-separated

filter by owner

page

results per page

page

results per page

page

results per page

page

results per page

Read time tracking: issue times, repo times, active stopwatches, your tracked times.

for 'list_issue_times'

for list_* methods

page

results per page

for list_* methods

Write time tracking: stopwatches and entries.

entry ID (for 'delete_time')

repo owner

repo name

seconds (for 'add_time')

Read wiki: list pages, get content, revision history.

repo owner

for 'get'/'get_revisions'

repo name

Write wiki pages: create, update, delete.

for 'create'/'update'

commit message

repo owner

for 'update'/'delete'

repo name

for 'create'


Prompt: Agrega un comentario 'modal de confirmacion 826' al issue infra-tools-156 de Jira.

addCommentToJiraIssue

Add or update a comment on a Jira issue

Cloud ID (UUID or site URL)

Comment body

ID of an existing comment to update. If omitted, a new comment is added.

Content format for body content. 'markdown' for simplified plain text. 'adf' (Atlassian Document Format, JSON) for full programmatic fidelity.

Issue ID or key (e.g., PROJ-123 or 10000)

addWorklogToJiraIssue

Add or update a worklog on a Jira issue. When worklogId is provided, updates that worklog;

Cloud ID (UUID or site URL)

Comment body

When the work was started (ISO 8601 date-time). If omitted, booked at current date/time.

Time spent (e.g. 2h, 30m, 4d). Required for new worklogs; use to set or change time when updating.

ID of an existing worklog to update. If omitted, a new worklog is created.

atlassianUserInfo

Get current user info

createCompassComponent

Create a new Compass component

Cloud ID (UUID or site URL)

Description of the component

Labels for the component

Name of the component

Owner ID of the component

Type ID of the component

createCompassComponentRelationship

Create a relationship between Compass components

Cloud ID (UUID or site URL)

The ARI of the source component

Type of relationship

The ARI of the target component

cloudId fromComponentId toComponentId relationshipType

createCompassCustomFieldDefinition

Create a custom field definition in Compass

Cloud ID (UUID or site URL)

Input data for creating the custom field definition

Description of the custom field definition

Whether the custom field is required

Name of the custom field definition

Type of the custom field

createConfluenceFooterComment

Create a footer comment on a page or blog post

Attachment ID to include

Page/comment body. HTML supports headings/paragraphs/tables/links/code/lists plus Confluence-specific data-type nodes (panels, status, task/decision lists, expands, layouts, cards, media, dates, mentions, macros/extensions, sync blocks). Never wrap in <html>/<head>/<body>.

Cloud ID (UUID or site URL)

Custom content ID to include

Parent comment ID for replies

createConfluenceInlineComment

Create an inline comment on specific text in a page or blog post. For top-level comments, provide pageId and inlineCommentProperties (text selection + match counts). For replies, provide parentCommentId only. Must first fetch the page content to find the exact text and count occurrences.

Same HTML/markdown/adf body format as createConfluencePage.

Cloud ID (UUID or site URL)

Required for top-level inline comments (not replies).

The exact text on the page to anchor the inline comment to. Must match rendered page text exactly (case-sensitive).

Total number of times textSelection appears on the page.

Zero-based index of the specific occurrence to anchor the comment to. Must be < textSelectionMatchCount.

Page or blog post ID or tiny link ID. Use for top-level inline comments only; not with parentCommentId.

Parent comment ID for replies. When provided, creates a reply; do not provide pageId/inlineCommentProperties.

createConfluencePage

Create a Confluence page or blog post

Page body. HTML: standard blocks (h1-h6, p, table/thead/tbody/tr/th/td, a, pre/code, ul/ol/li) plus Confluence HTML+ data-type nodes -- panels (panel-info/warning/note/success/error), status spans, task/decision lists, expand/details, layout sections, inline cards, dates, mentions, macros/extensions, sync blocks, media groups/inline media. Native macros use data-extension-type=com.atlassian.confluence.macro.core, never storage XML. Do not invent opaque IDs (data-user-id/data-id/data-collection/data-media-id/data-resource-id) -- only copy from existing content/tool output. ADF nesting rules apply (no self-nesting panels/expands/tables/blockquotes; list items/headings/captions are inline-only in some contexts). Never wrap in <html>/<head>/<body>.

Cloud ID (UUID or site URL)

Make private

Parent page ID (pages only, ignored for blogs)

Numeric space ID (a Long, e.g. '131073'). A space key (e.g. 'ENG') or personal-space key (e.g. '~712020abc') is also accepted and resolved automatically.

Status (draft for unpublished)

Page subtype (pages only, ignored for blogs)

Page or blog post title

createIssueLink

Create a link between two Jira issues. For directional link types (e.g. Blocks): inwardIssue = issue that blocks, outwardIssue = issue that is blocked (e.g. "A is blocked by B" -> inwardIssue: B, outwardIssue: A). Use getIssueLinkTypes if link type is unknown.

Cloud ID (UUID or site URL)

Optional comment on the outward issue.

Inward issue key (e.g. HSP-1).

Outward issue key (e.g. MKY-1).

Link type name (e.g. Duplicate, Blocks, Clones, Relates). Use getIssueLinkTypes to list available types.

createJiraIssue

Create a Jira issue. Use additional_fields to set any Jira field that does not have its own parameter (e.g. custom fields, priority, components).

REQUIRED for custom fields. The ONLY parameter to set priority, labels, custom fields, components, fix versions, or any other Jira fields not listed above. Examples: {"components": [{"name": "Backend"}]}, {"fixVersions": [{"name": "v1.2"}]}, {"priority": {"name": "High"}}, {"labels": ["bug"]}, {"customfield_10001": "value"}.

Assignee ID

Cloud ID (UUID or site URL)

Issue description. With contentFormat 'markdown' (default), plain text or Markdown string. With 'adf', an ADF JSON string or document object with type 'doc'.

Type (Task, Bug, Story)

Parent for subtasks

Project key

Optional workflow transition to apply during creation. Use getTransitionsForJiraIssue to find valid IDs. Placed at top level, not inside fields.

The workflow transition ID to apply during issue creation

cloudId projectKey issueTypeName summary

editJiraIssue

Update issue. After updating, returns the issue using the same default read fields as getJiraIssue (summary, description, status, issuetype, priority, labels, components, assignee, reporter, created, updated, resolution, project). Use getJiraIssue with fields ["*all"] or a custom list if you need more.

Cloud ID (UUID or site URL)

Fields to set, keyed by field name or customfield_* ID. To CLEAR a field, pass explicit null, e.g. { "resolution": null } -- fixes reopened issues blocked from transitioning because Resolution is still set.

Issue ID or key (e.g., PROJ-123 or 10000)

fetch

Get details of a Jira issue or Confluence page by ARI (Atlassian Resource Identifier), if the id is not an ARI, then use a different tool to fetch the content

Not needed for this tool -- cloudId is extracted from the ARI automatically

Atlassian Resource Identifier (ARI) from search results, e.g., 'ari:cloud:jira:cloudId:issue/10107' or 'ari:cloud:confluence:cloudId:page/123456789'

getAccessibleAtlassianResources

Get cloudId to make tool calls. When a link is provided (e.g. https://site.atlassian.net/*), try passing the site hostname as cloudId to other tools first; if that fails, use this tool to list accessible resources.

getCompassComponent

Get a Compass component by ID

Cloud ID (UUID or site URL)

The ID of the component to get

Whether to include custom fields in the response.

Whether to include related components and dependencies (all relationship types).

Whether to include related links (repository, documentation, Jira project, on-call, etc.).

getCompassComponents

Get a list of Compass components

The cursor to start at.

Cloud ID (UUID or site URL)

Additional filters -- results match ALL provided filters

Filter by component labels (e.g., ["frontend", "backend"]).

Filter by repository URLs -- reverse lookup a component by repo.

Filter by component type ids (e.g., ["SERVICE", "LIBRARY", "APPLICATION"]).

Max items per page.

The query to search for components.

getCompassCustomFieldDefinitions

Get a list of Compass custom field definitions

Cloud ID (UUID or site URL)

getConfluenceCommentChildren

Get reply(child) comments for a comment

Cloud ID (UUID or site URL)

Parent comment ID

Pagination cursor

Max replies

getConfluencePage

Get a Confluence page or blog post by ID, including body content.

Cloud ID (UUID or site URL)

'html' for structured HTML (round-trip safe, preserves inline comments/local IDs). 'markdown' for simplified plain text.

Page or blog post ID, or a Confluence tiny link ID (encoded part from /wiki/x/ URLs)

getConfluencePageDescendants

Get child pages of specified page

Cloud ID (UUID or site URL)

Pagination cursor

Max depth

Max descendants

getConfluencePageFooterComments

Get footer comments for a page or blog post

Cloud ID (UUID or site URL)

Pagination cursor

When true, also return reply comments

Max comments

current archived trashed deleted historical draft

getConfluencePageInlineComments

Get inline comments for a page or blog post

Cloud ID (UUID or site URL)

Pagination cursor

When true, also return reply comments

Max comments

getConfluenceSpaces

Get spaces

Cloud ID (UUID or site URL)

Properties to expand (string or array of strings)

User favorites

Favorite spaces only

Space IDs (string or array of numbers)

Space keys (string or array of strings)

Space labels (string or array of strings)

Max results (default: 25, max: 250)

Start index

getIssueLinkTypes

Get available Jira issue link types (e.g. Blocks, Duplicate, Clones, Relates). For createIssueLink: inwardIssue = blocker, outwardIssue = blocked (e.g. "A is blocked by B" -> inwardIssue: B, outwardIssue: A).

Cloud ID (UUID or site URL)

getJiraIssue

Get issue details

Cloud ID (UUID or site URL)

Additional issue details to expand (e.g. renderedFields, names).

Whether to fail quickly when some fields cannot be loaded instead of partially returning data.

Issue fields to return. Defaults to summary/description/status/issuetype/priority/labels/components/assignee/reporter/created/updated/resolution/project. Pass "*all" for every field. Include "comment" to get comments in fields.comment.comments.

Whether fields in the request are referenced by field keys instead of IDs.

Issue ID or key (e.g., PROJ-123 or 10000)

Issue property keys to include in the response.

Whether to update the user's recently viewed projects/history for this issue request.

getJiraIssueRemoteIssueLinks

Get remote links

Cloud ID (UUID or site URL)

getJiraIssueTypeMetaWithFields

Get field metadata

Cloud ID (UUID or site URL)

When true (default), returns only required fields to create an issue of this type. Set false for all fields.

getJiraProjectIssueTypesMetadata

Get issue types

Cloud ID (UUID or site URL)

getPagesInConfluenceSpace

Get pages or blog posts in a space

Cloud ID (UUID or site URL)

Pagination cursor

Max results (default: 25, max: 250)

id -id created-date -created-date modified-date -modified-date title -title

Space ID

Title filter

getTransitionsForJiraIssue

Get transitions

Cloud ID (UUID or site URL)

getVisibleJiraProjects

Get projects

Cloud ID (UUID or site URL)

lookupJiraAccountId

Lookup user IDs

Cloud ID (UUID or site URL)

search

Search Jira and Confluence using Rovo Search, ALWAYS use this tool to search for Jira and Confluence content unless the word CQL or JQL is used in the context

Not needed for this tool -- cloudId is derived from your access token automatically

The search query to use for Rovo Search

searchConfluenceUsingCql

Search Confluence content (pages, blog posts, comments, attachments) using CQL (Confluence Query Language). CQL is specific to Confluence and is not interchangeable with JQL.

Cloud ID (UUID or site URL)

CQL query string. Common fields: title, text, space, type, creator, contributor, label, ancestor, parent, lastmodified, created, mention, watcher, space.title, space.key. Use space key (not name) for the space field; use space.title ~ "name" for name search. Content types: page, blogpost, comment, attachment. Escape inner quotes with backslash.

CQL context for narrowing search scope (e.g., spaceKey)

Pagination cursor

Properties to expand

Max results (default: 25, max: 250)

Include next page link

Include previous page link

searchJiraIssuesUsingJql

Search issues with JQL, total counts only when explicitly requested.

Cloud ID (UUID or site URL)

Issue fields to return. Defaults as in getJiraIssue. Pass "*all" for every field. Include "comment" for comments.

JQL query

Max (50-100)

Page token

Default "issues". Never count for normal search or if nextPageToken used. Use "count" only when no trusted count exists and needed. Use "all" only if both required.

transitionJiraIssue

Transition issue status

Cloud ID (UUID or site URL)

updateConfluencePage

Update a Confluence page or blog post

Cloud ID (UUID or site URL)

If true, include the page body in the response; if false, omit to reduce payload size.

Parent page ID (pages only, ignored for blogs)

Space ID

New title

Version message


Prompt: Agrega un comentario 'landing page 338' al PR numero 457 de 'backend-core'.

Add review comment to the requester's latest pending pull request review. A pending review needs to already exist to call this (check with the user if not sure).

The text of the review comment

The line of the blob in the pull request diff that the comment applies to. For multi-line comments, the last line of the range

Repository owner

The relative path to the file that necessitates a comment

Pull request number

Repository name

The side of the diff to comment on. LEFT indicates the previous state, RIGHT indicates the new state

For multi-line comments, the first line of the range that the comment applies to

For multi-line comments, the starting side of the diff that the comment applies to

The level at which the comment is targeted

Add a comment to a specific issue in a GitHub repository. Use this tool to add comments to pull requests as well (in this case pass pull request number as issue_number), but only if user is not asking specifically to add review comments.

Comment content

Issue number to comment on

Repository owner

Repository name

Add a reply to an existing pull request comment. This creates a new comment that is linked as a reply to the specified comment.

The text of the reply

The ID of the comment to reply to

Repository owner

Pull request number

Repository name

Assign Copilot to a specific issue in a GitHub repository.

This tool can help with the following outcomes:
- a Pull Request created with source code changes to resolve the issue

More information can be found at:
- https://docs.github.com/en/copilot/using-github-copilot/using-copilot-coding-agent-to-work-on-tasks/about-assigning-tasks-to-copilot

Git reference (e.g., branch) that the agent will start its work from. If not specified, defaults to the repository's default branch

Optional custom instructions to guide the agent beyond the issue body.

Issue number

Repository owner

Repository name

Create a new branch in a GitHub repository

Name for new branch

Source branch (defaults to repo default)

Repository owner

Repository name

Create or update a single file in a GitHub repository.
If updating, you should provide the SHA of the file you want to update. Use this tool to create or update a file in a GitHub repository remotely; do not use it for local file operations.

In order to obtain the SHA of original file version before updating, use the following git command:
git rev-parse <branch>:<path to file>

SHA MUST be provided for existing file updates.

Branch to create/update the file in

Content of the file

Commit message

Repository owner (username or organization)

Path where to create/update the file

Repository name

The blob SHA of the file being replaced. Required if the file already exists.

Create a new pull request in a GitHub repository.

Branch to merge into

PR description

Create as draft PR

Branch containing changes

Allow maintainer edits

Repository owner

Repository name

PR title

Create a new GitHub repository in your account or specified organization

Initialize with README

Repository description

Repository name

Organization to create the repository in (omit to create in your personal account)

Whether repo should be private

Delete a file from a GitHub repository

Branch to delete the file from

Commit message

Path to the file to delete

Repository name

Fork a GitHub repository to your account or specified organization

Organization to fork to

Repository owner

Repository name

Get details for a commit from a GitHub repository

Whether to include file diffs and stats in the response. Default is true.

Repository owner

Page number for pagination (min 1)

Results per page for pagination (min 1, max 100)

Repository name

Commit SHA, branch name, or tag name

Get the contents of a file or directory from a GitHub repository

Path to file/directory

Accepts optional git refs such as `refs/tags/{tag}`, `refs/heads/{branch}` or `refs/pull/{pr_number}/head`

Repository name

Accepts optional commit SHA. If specified, it will be used instead of ref

Get a specific label from a repository.

Label name.

Repository owner (username or organization name)

Repository name

Get the latest release in a GitHub repository

Repository owner

Repository name

Get details of the authenticated GitHub user. Use this when a request is about the user's own profile for GitHub. Or when information is missing to build other tool calls.

Get a specific release by its tag name in a GitHub repository

Repository owner

Repository name

Tag name (e.g., 'v1.0.0')

Get details about a specific git tag in a GitHub repository

Repository owner

Repository name

Tag name

Get member usernames of a specific team in an organization. Limited to organizations accessible with current credentials

Organization login (owner) that contains the team.

Team slug

Get details of the teams the user is a member of. Limited to organizations accessible with current credentials

Username to get teams for. If not provided, uses the authenticated user.

Get information about a specific issue in a GitHub repository.

The number of the issue

1. get - Get details of a specific issue. 2. get_comments - Get issue comments. 3. get_sub_issues - Get sub-issues of the issue. 4. get_labels - Get labels assigned to the issue.

The owner of the repository

Page number for pagination (min 1)

The name of the repository

Create a new or update an existing issue in a GitHub repository.

Usernames to assign to this issue

Issue body content

Issue number that this issue is a duplicate of. Only used when state_reason is 'duplicate'.

Issue number to update

Labels to apply to this issue

'create' creates a new issue. 'update' updates an existing issue.

Milestone number

Repository owner

Repository name

New state

Reason for the state change. Ignored unless state is changed.

Issue title

Type of this issue. Only use if the repository has issue types configured.

List branches in a GitHub repository

Repository owner

Page number for pagination (min 1)

Results per page for pagination (min 1, max 100)

Repository name

Get list of commits of a branch in a GitHub repository. Returns at least 30 results per page by default, but can return more if specified using the perPage parameter (up to 100).

Author username or email address to filter commits by

Repository owner

Page number for pagination (min 1)

Only commits containing this file path will be returned

Repository name

Commit SHA, branch or tag name to list commits of. Defaults to the default branch.

Only commits after this date (ISO 8601)

Only commits before this date (ISO 8601)

List supported issue types for repository owner (organization).

The organization owner of the repository

List issues in a GitHub repository. For pagination, use the 'endCursor' from the previous response's 'pageInfo' in the 'after' parameter.

Cursor for pagination.

Order direction. Requires 'orderBy' too.

Filter by labels

Order issues by field. Requires 'direction' too.

Repository owner

Repository name

Filter by date (ISO 8601 timestamp)

Filter by state

List pull requests in a GitHub repository. If the user specifies an author, then DO NOT use this tool and use the search_pull_requests tool instead.

Filter by base branch

Sort direction

Filter by head user/org and branch

Repository owner

Page number for pagination (min 1)

Repository name

Sort by

Filter by state

List releases in a GitHub repository

Repository owner

Page number for pagination (min 1)

Repository name

List collaborators of a GitHub repository. Results are paginated; the response includes `nextPage`, `prevPage`, `firstPage`, and `lastPage` fields. To get the next page, use the `nextPage` value as the `page` parameter.

Filter by affiliation. Default: 'all'

Repository owner

Page number for pagination (default 1, min 1)

Results per page for pagination (default 30, min 1, max 100)

Repository name

List git tags in a GitHub repository

Repository owner

Page number for pagination (min 1)

Repository name

Merge a pull request in a GitHub repository.

Extra detail for merge commit

Title for merge commit

Merge method

Repository owner

Pull request number

Repository name

Get information on a specific pull request in GitHub repository.

Cursor for pagination, used only by get_review_comments.

1. get 2. get_diff 3. get_status 4. get_files 5. get_review_comments 6. get_reviews 7. get_comments 8. get_check_runs

Repository owner

Page number for pagination (min 1)

Results per page for pagination (min 1, max 100)

Pull request number

Repository name

Create and/or submit, delete review of a pull request.

- create: Create a new review of a pull request. If "event" is provided, the review is submitted; if omitted, a pending review is created.
- submit_pending: Submit an existing pending review.
- delete_pending: Delete an existing pending review.
- resolve_thread / unresolve_thread: only need "threadId".

Review comment text

SHA of commit to review

Review action to perform.

Repository owner

Pull request number

Repository name

Node ID of the review thread (e.g., PRRT_kwDOxxx). Required for resolve/unresolve_thread.

Push multiple files to a GitHub repository in a single commit

Branch to push to

Array of file objects to push, each object with path (string) and content (string)

file content

path to the file

Commit message

Repository owner

Repository name

Request a GitHub Copilot code review for a pull request. Use this for automated feedback on pull requests, usually before requesting a human reviewer.

Repository owner

Pull request number

Repository name

Fast and precise code search across ALL GitHub repositories using GitHub's native search engine. Best for finding exact symbols, functions, classes, or specific code patterns.

Sort order for results

Page number for pagination (min 1)

Search query (GitHub code search REST). Supports OR/NOT/quoted phrases and qualifiers repo:/org:/user:/language:/path:/filename:/extension:/in:file/in:path/size:/is:archived/is:fork. Max 256 chars.

Sort field ('indexed' only)

Search for commits across GitHub repositories using GitHub's commit search syntax. Searches the default branch only.

Sort order

Page number for pagination (min 1)

Commit search query. Scope with repo:/org:/user:. Other qualifiers: author:, committer:, author-date:, merge:, hash:, tree:, parent:, is:public.

Sort by author or committer date (defaults to best match)

Search for issues in GitHub repositories using issues search syntax already scoped to is:issue

Sort order

Optional repository owner. If provided with repo, only issues for this repository are listed.

Page number for pagination (min 1)

Search query using GitHub issues search syntax

Optional repository name. If provided with owner, only issues for this repository are listed.

Sort field by number of matches of categories, defaults to best match

Search for pull requests in GitHub repositories using issues search syntax already scoped to is:pr

Sort order

Optional repository owner. If provided with repo, only pull requests for this repository are listed.

Page number for pagination (min 1)

Search query using GitHub pull request search syntax

Optional repository name. If provided with owner, only pull requests for this repository are listed.

Find GitHub repositories by name, description, readme, topics, or other metadata. Perfect for discovering projects, finding examples, or locating specific repositories across GitHub.

Return minimal repository information (default: true). When false, returns full GitHub API repository objects.

Sort order

Page number for pagination (min 1)

Results per page for pagination (min 1, max 100)

Repository search query. Examples: 'machine learning in:name stars:>1000 language:python', 'topic:react', 'user:facebook'.

Sort repositories by field, defaults to best match

Find GitHub users by username, real name, or other profile information. Useful for locating developers, contributors, or team members.

Sort order

Page number for pagination (min 1)

User search query. Examples: 'john smith', 'location:seattle', 'followers:>100'. Search is automatically scoped to type:user.

Sort users by number of followers or repositories, or when the person joined GitHub.

Update an existing pull request in a GitHub repository.

New base branch name

New description

Mark pull request as draft (true) or ready for review (false)

Allow maintainer edits

Repository owner

Pull request number to update

Repository name

GitHub usernames to request reviews from

New state

New title

Update the branch of a pull request with the latest changes from the base branch.

The expected SHA of the pull request's HEAD ref

Repository owner

Pull request number

Repository name

Add a sub-issue to a parent issue in a GitHub repository.

The ID of the sub-issue to be prioritized after (either after_id OR before_id should be specified)

The ID of the sub-issue to be prioritized before (either after_id OR before_id should be specified)

The number of the parent issue

'add' - add a sub-issue to a parent issue. 'remove' - remove a sub-issue from a parent issue. 'reprioritize' - change the order of sub-issues within a parent issue, using 'after_id' or 'before_id'.

Repository owner

When true, replaces the sub-issue's current parent issue. Use with 'add' method only.

Repository name

The ID of the sub-issue to add. ID is not the same as issue number


Prompt: Crea un issue en 'mobile-client' titulado 'panel de admin 953' asignado a mi usuario.

Add review comment to the requester's latest pending pull request review. A pending review needs to already exist to call this (check with the user if not sure).

The text of the review comment

The line of the blob in the pull request diff that the comment applies to. For multi-line comments, the last line of the range

Repository owner

The relative path to the file that necessitates a comment

Pull request number

Repository name

The side of the diff to comment on. LEFT indicates the previous state, RIGHT indicates the new state

For multi-line comments, the first line of the range that the comment applies to

For multi-line comments, the starting side of the diff that the comment applies to

The level at which the comment is targeted

Add a comment to a specific issue in a GitHub repository. Use this tool to add comments to pull requests as well (in this case pass pull request number as issue_number), but only if user is not asking specifically to add review comments.

Comment content

Issue number to comment on

Repository owner

Repository name

Add a reply to an existing pull request comment. This creates a new comment that is linked as a reply to the specified comment.

The text of the reply

The ID of the comment to reply to

Repository owner

Pull request number

Repository name

Assign Copilot to a specific issue in a GitHub repository.

This tool can help with the following outcomes:
- a Pull Request created with source code changes to resolve the issue

More information can be found at:
- https://docs.github.com/en/copilot/using-github-copilot/using-copilot-coding-agent-to-work-on-tasks/about-assigning-tasks-to-copilot

Git reference (e.g., branch) that the agent will start its work from. If not specified, defaults to the repository's default branch

Optional custom instructions to guide the agent beyond the issue body.

Issue number

Repository owner

Repository name

Create a new branch in a GitHub repository

Name for new branch

Source branch (defaults to repo default)

Repository owner

Repository name

Create or update a single file in a GitHub repository.
If updating, you should provide the SHA of the file you want to update. Use this tool to create or update a file in a GitHub repository remotely; do not use it for local file operations.

In order to obtain the SHA of original file version before updating, use the following git command:
git rev-parse <branch>:<path to file>

SHA MUST be provided for existing file updates.

Branch to create/update the file in

Content of the file

Commit message

Repository owner (username or organization)

Path where to create/update the file

Repository name

The blob SHA of the file being replaced. Required if the file already exists.

Create a new pull request in a GitHub repository.

Branch to merge into

PR description

Create as draft PR

Branch containing changes

Allow maintainer edits

Repository owner

Repository name

PR title

Create a new GitHub repository in your account or specified organization

Initialize with README

Repository description

Repository name

Organization to create the repository in (omit to create in your personal account)

Whether repo should be private

Delete a file from a GitHub repository

Branch to delete the file from

Commit message

Path to the file to delete

Repository name

Fork a GitHub repository to your account or specified organization

Organization to fork to

Repository owner

Repository name

Get details for a commit from a GitHub repository

Whether to include file diffs and stats in the response. Default is true.

Repository owner

Page number for pagination (min 1)

Results per page for pagination (min 1, max 100)

Repository name

Commit SHA, branch name, or tag name

Get the contents of a file or directory from a GitHub repository

Path to file/directory

Accepts optional git refs such as `refs/tags/{tag}`, `refs/heads/{branch}` or `refs/pull/{pr_number}/head`

Repository name

Accepts optional commit SHA. If specified, it will be used instead of ref

Get a specific label from a repository.

Label name.

Repository owner (username or organization name)

Repository name

Get the latest release in a GitHub repository

Repository owner

Repository name

Get details of the authenticated GitHub user. Use this when a request is about the user's own profile for GitHub. Or when information is missing to build other tool calls.

Get a specific release by its tag name in a GitHub repository

Repository owner

Repository name

Tag name (e.g., 'v1.0.0')

Get details about a specific git tag in a GitHub repository

Repository owner

Repository name

Tag name

Get member usernames of a specific team in an organization. Limited to organizations accessible with current credentials

Organization login (owner) that contains the team.

Team slug

Get details of the teams the user is a member of. Limited to organizations accessible with current credentials

Username to get teams for. If not provided, uses the authenticated user.

Get information about a specific issue in a GitHub repository.

The number of the issue

1. get - Get details of a specific issue. 2. get_comments - Get issue comments. 3. get_sub_issues - Get sub-issues of the issue. 4. get_labels - Get labels assigned to the issue.

The owner of the repository

Page number for pagination (min 1)

The name of the repository

Create a new or update an existing issue in a GitHub repository.

Usernames to assign to this issue

Issue body content

Issue number that this issue is a duplicate of. Only used when state_reason is 'duplicate'.

Issue number to update

Labels to apply to this issue

'create' creates a new issue. 'update' updates an existing issue.

Milestone number

Repository owner

Repository name

New state

Reason for the state change. Ignored unless state is changed.

Issue title

Type of this issue. Only use if the repository has issue types configured.

List branches in a GitHub repository

Repository owner

Page number for pagination (min 1)

Results per page for pagination (min 1, max 100)

Repository name

Get list of commits of a branch in a GitHub repository. Returns at least 30 results per page by default, but can return more if specified using the perPage parameter (up to 100).

Author username or email address to filter commits by

Repository owner

Page number for pagination (min 1)

Only commits containing this file path will be returned

Repository name

Commit SHA, branch or tag name to list commits of. Defaults to the default branch.

Only commits after this date (ISO 8601)

Only commits before this date (ISO 8601)

List supported issue types for repository owner (organization).

The organization owner of the repository

List issues in a GitHub repository. For pagination, use the 'endCursor' from the previous response's 'pageInfo' in the 'after' parameter.

Cursor for pagination.

Order direction. Requires 'orderBy' too.

Filter by labels

Order issues by field. Requires 'direction' too.

Repository owner

Repository name

Filter by date (ISO 8601 timestamp)

Filter by state

List pull requests in a GitHub repository. If the user specifies an author, then DO NOT use this tool and use the search_pull_requests tool instead.

Filter by base branch

Sort direction

Filter by head user/org and branch

Repository owner

Page number for pagination (min 1)

Repository name

Sort by

Filter by state

List releases in a GitHub repository

Repository owner

Page number for pagination (min 1)

Repository name

List collaborators of a GitHub repository. Results are paginated; the response includes `nextPage`, `prevPage`, `firstPage`, and `lastPage` fields. To get the next page, use the `nextPage` value as the `page` parameter.

Filter by affiliation. Default: 'all'

Repository owner

Page number for pagination (default 1, min 1)

Results per page for pagination (default 30, min 1, max 100)

Repository name

List git tags in a GitHub repository

Repository owner

Page number for pagination (min 1)

Repository name

Merge a pull request in a GitHub repository.

Extra detail for merge commit

Title for merge commit

Merge method

Repository owner

Pull request number

Repository name

Get information on a specific pull request in GitHub repository.

Cursor for pagination, used only by get_review_comments.

1. get 2. get_diff 3. get_status 4. get_files 5. get_review_comments 6. get_reviews 7. get_comments 8. get_check_runs

Repository owner

Page number for pagination (min 1)

Results per page for pagination (min 1, max 100)

Pull request number

Repository name

Create and/or submit, delete review of a pull request.

- create: Create a new review of a pull request. If "event" is provided, the review is submitted; if omitted, a pending review is created.
- submit_pending: Submit an existing pending review.
- delete_pending: Delete an existing pending review.
- resolve_thread / unresolve_thread: only need "threadId".

Review comment text

SHA of commit to review

Review action to perform.

Repository owner

Pull request number

Repository name

Node ID of the review thread (e.g., PRRT_kwDOxxx). Required for resolve/unresolve_thread.

Push multiple files to a GitHub repository in a single commit

Branch to push to

Array of file objects to push, each object with path (string) and content (string)

file content

path to the file

Commit message

Repository owner

Repository name

Request a GitHub Copilot code review for a pull request. Use this for automated feedback on pull requests, usually before requesting a human reviewer.

Repository owner

Pull request number

Repository name

Fast and precise code search across ALL GitHub repositories using GitHub's native search engine. Best for finding exact symbols, functions, classes, or specific code patterns.

Sort order for results

Page number for pagination (min 1)

Search query (GitHub code search REST). Supports OR/NOT/quoted phrases and qualifiers repo:/org:/user:/language:/path:/filename:/extension:/in:file/in:path/size:/is:archived/is:fork. Max 256 chars.

Sort field ('indexed' only)

Search for commits across GitHub repositories using GitHub's commit search syntax. Searches the default branch only.

Sort order

Page number for pagination (min 1)

Commit search query. Scope with repo:/org:/user:. Other qualifiers: author:, committer:, author-date:, merge:, hash:, tree:, parent:, is:public.

Sort by author or committer date (defaults to best match)

Search for issues in GitHub repositories using issues search syntax already scoped to is:issue

Sort order

Optional repository owner. If provided with repo, only issues for this repository are listed.

Page number for pagination (min 1)

Search query using GitHub issues search syntax

Optional repository name. If provided with owner, only issues for this repository are listed.

Sort field by number of matches of categories, defaults to best match

Search for pull requests in GitHub repositories using issues search syntax already scoped to is:pr

Sort order

Optional repository owner. If provided with repo, only pull requests for this repository are listed.

Page number for pagination (min 1)

Search query using GitHub pull request search syntax

Optional repository name. If provided with owner, only pull requests for this repository are listed.

Find GitHub repositories by name, description, readme, topics, or other metadata. Perfect for discovering projects, finding examples, or locating specific repositories across GitHub.

Return minimal repository information (default: true). When false, returns full GitHub API repository objects.

Sort order

Page number for pagination (min 1)

Results per page for pagination (min 1, max 100)

Repository search query. Examples: 'machine learning in:name stars:>1000 language:python', 'topic:react', 'user:facebook'.

Sort repositories by field, defaults to best match

Find GitHub users by username, real name, or other profile information. Useful for locating developers, contributors, or team members.

Sort order

Page number for pagination (min 1)

User search query. Examples: 'john smith', 'location:seattle', 'followers:>100'. Search is automatically scoped to type:user.

Sort users by number of followers or repositories, or when the person joined GitHub.

Update an existing pull request in a GitHub repository.

New base branch name

New description

Mark pull request as draft (true) or ready for review (false)

Allow maintainer edits

Repository owner

Pull request number to update

Repository name

GitHub usernames to request reviews from

New state

New title

Update the branch of a pull request with the latest changes from the base branch.

The expected SHA of the pull request's HEAD ref

Repository owner

Pull request number

Repository name

Add a sub-issue to a parent issue in a GitHub repository.

The ID of the sub-issue to be prioritized after (either after_id OR before_id should be specified)

The ID of the sub-issue to be prioritized before (either after_id OR before_id should be specified)

The number of the parent issue

'add' - add a sub-issue to a parent issue. 'remove' - remove a sub-issue from a parent issue. 'reprioritize' - change the order of sub-issues within a parent issue, using 'after_id' or 'before_id'.

Repository owner

When true, replaces the sub-issue's current parent issue. Use with 'add' method only.

Repository name

The ID of the sub-issue to add. ID is not the same as issue number


Prompt: Agrega un board nuevo llamado 'Dashboard Principal' de 480x60 px en la pagina actual.

Executes JavaScript code in the Penpot plugin context.
IMPORTANT: Before using this tool, make sure you have read the 'Penpot High-Level Overview' and know which Penpot API functionality is necessary and how to use it.
You have access two main objects: `penpot` (the Penpot API, of type `Penpot`), `penpotUtils`, and `storage`.
`storage` is an object in which arbitrary data can be stored, simply by adding a new attribute; stored attributes can be referenced in future calls to this tool, so any intermediate results that could come in handy later should be stored in `storage` instead of just a fleeting variable; you can also store functions and thus build up a library).
Think of the code being executed as the body of a function: The tool call returns whatever you return in the applicable `return` statement, if any.
If an exception occurs, the exception's message will be returned to you.
Any output that you generate via the `console` object will be returned to you separately; so you may use itto track what your code is doing, but you should *only* do so only if there is an ACTUAL NEED for this! VERY IMPORTANT: Don't use logging prematurely! NEVER log the data you are returning, as you will otherwise receive it twice!
VERY IMPORTANT: In general, try a simple approach first, and only if it fails, try more complex code that involves handling different cases (in particular error cases) and that applies logging.

The JavaScript code to execute in the plugin context.

Exports a shape (or a shape's image fill) from the Penpot design to a PNG or SVG image, such that you can get an impression of what it looks like.

Identifier of the shape to export. Use the special identifier 'selection' to export the first shape currently selected by the user.

The output format, either 'png' (default) or 'svg'.

The export mode: either 'shape' (full shape as it appears in the design, including descendants; the default) or 'fill' (export the raw image that is used as a fill for the shape; PNG format only)

En despliegues con filesystem habilitado, el schema oficial incluye ademas un parametro opcional 'filePath' (para guardar el export a disco) y la descripcion agrega 'Alternatively, you can save it to a file.'. En este deployment (remoto/multi-usuario) 'filePath' esta eliminado del schema y esa frase no aparece -- ver PENPOT_DEPLOYMENT_NOTES.md.

Returns basic high-level instructions on the usage of Penpot-related tools and the Penpot API. If you have already read the 'Penpot High-Level Overview', you must not call this tool.

Retrieves Penpot API documentation for types and their members.Be sure to read the 'Penpot High-Level Overview' first.


Prompt: Busca en Docmost paginas que mencionen 'login 251'.

Check for new comments across pages in a space since a given timestamp. Optionally scope to a page subtree (folder). Returns only comments created after the specified time.

Space ID to check for new comments

ISO 8601 timestamp — only return comments created after this time (e.g. '2026-03-10T00:00:00Z')

Optional root page ID to scope the check to a subtree (folder). Only pages under this parent will be checked.

Create a new comment on a page. Content is provided as Markdown and automatically converted to the required format.

ID of the page to comment on

Comment content in Markdown format

Parent comment ID to create a reply (max 2 nesting levels)

Selected text for inline comments (max 250 chars). Required when type is 'inline'.

Comment type: 'page' for general page comment (default), 'inline' for text selection comment

Create a new page with content (automatically moves it to the correct hierarchy).

Title of the page

Markdown content

Optional parent page ID to nest under

Delete a comment. Only the comment creator or space admin can delete it.

ID of the comment to delete

Delete a single page by ID.

Delete multiple pages at once. Useful for cleanup.

Get a single comment by ID with content as Markdown.

ID of the comment

Get details and content of a specific page by ID

Get the current Docmost workspace

List all comments on a page. Returns comments with content converted to Markdown.

ID of the page to list comments for

List all available groups in Docmost

List pages in a space ordered by updatedAt (descending).

List all available spaces in Docmost

Move a page to a new parent (nesting) or root. Essential for organizing pages created via 'import_page'.

Target parent page ID. Pass 'null' or empty string to move to root.

Optional position string (5-12 chars). Defaults to 'a00000' (end) if omitted.

search

Search for pages and content.

Search query

Optional space ID to filter by

Update an existing comment's content. Only the comment creator can update it. Content is provided as Markdown.

ID of the comment to update

New comment content in Markdown format

Update a page's content and/or title via realtime collaboration (preserves Page ID and history).

ID of the page to update

New Markdown content

Optional new title


Prompt: Crea un rectangulo de 320x60 en el board 'Checkout Flow' con color #188038.

Executes JavaScript code in the Penpot plugin context.
IMPORTANT: Before using this tool, make sure you have read the 'Penpot High-Level Overview' and know which Penpot API functionality is necessary and how to use it.
You have access two main objects: `penpot` (the Penpot API, of type `Penpot`), `penpotUtils`, and `storage`.
`storage` is an object in which arbitrary data can be stored, simply by adding a new attribute; stored attributes can be referenced in future calls to this tool, so any intermediate results that could come in handy later should be stored in `storage` instead of just a fleeting variable; you can also store functions and thus build up a library).
Think of the code being executed as the body of a function: The tool call returns whatever you return in the applicable `return` statement, if any.
If an exception occurs, the exception's message will be returned to you.
Any output that you generate via the `console` object will be returned to you separately; so you may use itto track what your code is doing, but you should *only* do so only if there is an ACTUAL NEED for this! VERY IMPORTANT: Don't use logging prematurely! NEVER log the data you are returning, as you will otherwise receive it twice!
VERY IMPORTANT: In general, try a simple approach first, and only if it fails, try more complex code that involves handling different cases (in particular error cases) and that applies logging.

The JavaScript code to execute in the plugin context.

Exports a shape (or a shape's image fill) from the Penpot design to a PNG or SVG image, such that you can get an impression of what it looks like.

Identifier of the shape to export. Use the special identifier 'selection' to export the first shape currently selected by the user.

The output format, either 'png' (default) or 'svg'.

The export mode: either 'shape' (full shape as it appears in the design, including descendants; the default) or 'fill' (export the raw image that is used as a fill for the shape; PNG format only)

Returns basic high-level instructions on the usage of Penpot-related tools and the Penpot API. If you have already read the 'Penpot High-Level Overview', you must not call this tool.

Retrieves Penpot API documentation for types and their members.Be sure to read the 'Penpot High-Level Overview' first.


Prompt: Lista los issues abiertos de 'infra-tools' con label 'enhancement'.

Add review comment to the requester's latest pending pull request review. A pending review needs to already exist to call this (check with the user if not sure).

The text of the review comment

The line of the blob in the pull request diff that the comment applies to. For multi-line comments, the last line of the range

Repository owner

The relative path to the file that necessitates a comment

Pull request number

Repository name

The side of the diff to comment on. LEFT indicates the previous state, RIGHT indicates the new state

For multi-line comments, the first line of the range that the comment applies to

For multi-line comments, the starting side of the diff that the comment applies to

The level at which the comment is targeted

Add a comment to a specific issue in a GitHub repository. Use this tool to add comments to pull requests as well (in this case pass pull request number as issue_number), but only if user is not asking specifically to add review comments.

Comment content

Issue number to comment on

Repository owner

Repository name

Add a reply to an existing pull request comment. This creates a new comment that is linked as a reply to the specified comment.

The text of the reply

The ID of the comment to reply to

Repository owner

Pull request number

Repository name

Assign Copilot to a specific issue in a GitHub repository.

This tool can help with the following outcomes:
- a Pull Request created with source code changes to resolve the issue

More information can be found at:
- https://docs.github.com/en/copilot/using-github-copilot/using-copilot-coding-agent-to-work-on-tasks/about-assigning-tasks-to-copilot

Git reference (e.g., branch) that the agent will start its work from. If not specified, defaults to the repository's default branch

Optional custom instructions to guide the agent beyond the issue body.

Issue number

Repository owner

Repository name

Create a new branch in a GitHub repository

Name for new branch

Source branch (defaults to repo default)

Repository owner

Repository name

Create or update a single file in a GitHub repository.
If updating, you should provide the SHA of the file you want to update. Use this tool to create or update a file in a GitHub repository remotely; do not use it for local file operations.

In order to obtain the SHA of original file version before updating, use the following git command:
git rev-parse <branch>:<path to file>

SHA MUST be provided for existing file updates.

Branch to create/update the file in

Content of the file

Commit message

Repository owner (username or organization)

Path where to create/update the file

Repository name

The blob SHA of the file being replaced. Required if the file already exists.

Create a new pull request in a GitHub repository.

Branch to merge into

PR description

Create as draft PR

Branch containing changes

Allow maintainer edits

Repository owner

Repository name

PR title

Create a new GitHub repository in your account or specified organization

Initialize with README

Repository description

Repository name

Organization to create the repository in (omit to create in your personal account)

Whether repo should be private

Delete a file from a GitHub repository

Branch to delete the file from

Commit message

Path to the file to delete

Repository name

Fork a GitHub repository to your account or specified organization

Organization to fork to

Repository owner

Repository name

Get details for a commit from a GitHub repository

Whether to include file diffs and stats in the response. Default is true.

Repository owner

Page number for pagination (min 1)

Results per page for pagination (min 1, max 100)

Repository name

Commit SHA, branch name, or tag name

Get the contents of a file or directory from a GitHub repository

Path to file/directory

Accepts optional git refs such as `refs/tags/{tag}`, `refs/heads/{branch}` or `refs/pull/{pr_number}/head`

Repository name

Accepts optional commit SHA. If specified, it will be used instead of ref

Get a specific label from a repository.

Label name.

Repository owner (username or organization name)

Repository name

Get the latest release in a GitHub repository

Repository owner

Repository name

Get details of the authenticated GitHub user. Use this when a request is about the user's own profile for GitHub. Or when information is missing to build other tool calls.

Get a specific release by its tag name in a GitHub repository

Repository owner

Repository name

Tag name (e.g., 'v1.0.0')

Get details about a specific git tag in a GitHub repository

Repository owner

Repository name

Tag name

Get member usernames of a specific team in an organization. Limited to organizations accessible with current credentials

Organization login (owner) that contains the team.

Team slug

Get details of the teams the user is a member of. Limited to organizations accessible with current credentials

Username to get teams for. If not provided, uses the authenticated user.

Get information about a specific issue in a GitHub repository.

The number of the issue

1. get - Get details of a specific issue. 2. get_comments - Get issue comments. 3. get_sub_issues - Get sub-issues of the issue. 4. get_labels - Get labels assigned to the issue.

The owner of the repository

Page number for pagination (min 1)

The name of the repository

Create a new or update an existing issue in a GitHub repository.

Usernames to assign to this issue

Issue body content

Issue number that this issue is a duplicate of. Only used when state_reason is 'duplicate'.

Issue number to update

Labels to apply to this issue

'create' creates a new issue. 'update' updates an existing issue.

Milestone number

Repository owner

Repository name

New state

Reason for the state change. Ignored unless state is changed.

Issue title

Type of this issue. Only use if the repository has issue types configured.

List branches in a GitHub repository

Repository owner

Page number for pagination (min 1)

Results per page for pagination (min 1, max 100)

Repository name

Get list of commits of a branch in a GitHub repository. Returns at least 30 results per page by default, but can return more if specified using the perPage parameter (up to 100).

Author username or email address to filter commits by

Repository owner

Page number for pagination (min 1)

Only commits containing this file path will be returned

Repository name

Commit SHA, branch or tag name to list commits of. Defaults to the default branch.

Only commits after this date (ISO 8601)

Only commits before this date (ISO 8601)

List supported issue types for repository owner (organization).

The organization owner of the repository

List issues in a GitHub repository. For pagination, use the 'endCursor' from the previous response's 'pageInfo' in the 'after' parameter.

Cursor for pagination.

Order direction. Requires 'orderBy' too.

Filter by labels

Order issues by field. Requires 'direction' too.

Repository owner

Repository name

Filter by date (ISO 8601 timestamp)

Filter by state

List pull requests in a GitHub repository. If the user specifies an author, then DO NOT use this tool and use the search_pull_requests tool instead.

Filter by base branch

Sort direction

Filter by head user/org and branch

Repository owner

Page number for pagination (min 1)

Repository name

Sort by

Filter by state

List releases in a GitHub repository

Repository owner

Page number for pagination (min 1)

Repository name

List collaborators of a GitHub repository. Results are paginated; the response includes `nextPage`, `prevPage`, `firstPage`, and `lastPage` fields. To get the next page, use the `nextPage` value as the `page` parameter.

Filter by affiliation. Default: 'all'

Repository owner

Page number for pagination (default 1, min 1)

Results per page for pagination (default 30, min 1, max 100)

Repository name

List git tags in a GitHub repository

Repository owner

Page number for pagination (min 1)

Repository name

Merge a pull request in a GitHub repository.

Extra detail for merge commit

Title for merge commit

Merge method

Repository owner

Pull request number

Repository name

Get information on a specific pull request in GitHub repository.

Cursor for pagination, used only by get_review_comments.

1. get 2. get_diff 3. get_status 4. get_files 5. get_review_comments 6. get_reviews 7. get_comments 8. get_check_runs

Repository owner

Page number for pagination (min 1)

Results per page for pagination (min 1, max 100)

Pull request number

Repository name

Create and/or submit, delete review of a pull request.

- create: Create a new review of a pull request. If "event" is provided, the review is submitted; if omitted, a pending review is created.
- submit_pending: Submit an existing pending review.
- delete_pending: Delete an existing pending review.
- resolve_thread / unresolve_thread: only need "threadId".

Review comment text

SHA of commit to review

Review action to perform.

Repository owner

Pull request number

Repository name

Node ID of the review thread (e.g., PRRT_kwDOxxx). Required for resolve/unresolve_thread.

Push multiple files to a GitHub repository in a single commit

Branch to push to

Array of file objects to push, each object with path (string) and content (string)

file content

path to the file

Commit message

Repository owner

Repository name

Request a GitHub Copilot code review for a pull request. Use this for automated feedback on pull requests, usually before requesting a human reviewer.

Repository owner

Pull request number

Repository name

Fast and precise code search across ALL GitHub repositories using GitHub's native search engine. Best for finding exact symbols, functions, classes, or specific code patterns.

Sort order for results

Page number for pagination (min 1)

Search query (GitHub code search REST). Supports OR/NOT/quoted phrases and qualifiers repo:/org:/user:/language:/path:/filename:/extension:/in:file/in:path/size:/is:archived/is:fork. Max 256 chars.

Sort field ('indexed' only)

Search for commits across GitHub repositories using GitHub's commit search syntax. Searches the default branch only.

Sort order

Page number for pagination (min 1)

Commit search query. Scope with repo:/org:/user:. Other qualifiers: author:, committer:, author-date:, merge:, hash:, tree:, parent:, is:public.

Sort by author or committer date (defaults to best match)

Search for issues in GitHub repositories using issues search syntax already scoped to is:issue

Sort order

Optional repository owner. If provided with repo, only issues for this repository are listed.

Page number for pagination (min 1)

Search query using GitHub issues search syntax

Optional repository name. If provided with owner, only issues for this repository are listed.

Sort field by number of matches of categories, defaults to best match

Search for pull requests in GitHub repositories using issues search syntax already scoped to is:pr

Sort order

Optional repository owner. If provided with repo, only pull requests for this repository are listed.

Page number for pagination (min 1)

Search query using GitHub pull request search syntax

Optional repository name. If provided with owner, only pull requests for this repository are listed.

Find GitHub repositories by name, description, readme, topics, or other metadata. Perfect for discovering projects, finding examples, or locating specific repositories across GitHub.

Return minimal repository information (default: true). When false, returns full GitHub API repository objects.

Sort order

Page number for pagination (min 1)

Results per page for pagination (min 1, max 100)

Repository search query. Examples: 'machine learning in:name stars:>1000 language:python', 'topic:react', 'user:facebook'.

Sort repositories by field, defaults to best match

Find GitHub users by username, real name, or other profile information. Useful for locating developers, contributors, or team members.

Sort order

Page number for pagination (min 1)

User search query. Examples: 'john smith', 'location:seattle', 'followers:>100'. Search is automatically scoped to type:user.

Sort users by number of followers or repositories, or when the person joined GitHub.

Update an existing pull request in a GitHub repository.

New base branch name

New description

Mark pull request as draft (true) or ready for review (false)

Allow maintainer edits

Repository owner

Pull request number to update

Repository name

GitHub usernames to request reviews from

New state

New title

Update the branch of a pull request with the latest changes from the base branch.

The expected SHA of the pull request's HEAD ref

Repository owner

Pull request number

Repository name

Add a sub-issue to a parent issue in a GitHub repository.

The ID of the sub-issue to be prioritized after (either after_id OR before_id should be specified)

The ID of the sub-issue to be prioritized before (either after_id OR before_id should be specified)

The number of the parent issue

'add' - add a sub-issue to a parent issue. 'remove' - remove a sub-issue from a parent issue. 'reprioritize' - change the order of sub-issues within a parent issue, using 'after_id' or 'before_id'.

Repository owner

When true, replaces the sub-issue's current parent issue. Use with 'add' method only.

Repository name

The ID of the sub-issue to add. ID is not the same as issue number