Skip to main content
Glama
garc33

Bitbucket Server MCP

by garc33
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_activities

Retrieve all activities for a pull request including comments, reviews, commits, and other timeline events. Use this to get the complete activity history and timeline of the pull request.

Instructions

Retrieve all activities for a pull request including comments, reviews, commits, and other timeline events. Use this to get the complete activity history and timeline of the pull request.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
prIdYesPull request ID to get activities for.
limitNoMaximum number of activities to return per page (default: 25, max: 100).
startNoPage offset (0-based). Use nextPageStart from a previous response to fetch the next page.
projectNoBitbucket project key. If omitted, uses BITBUCKET_DEFAULT_PROJECT environment variable.
fetchAllNoWhen true, fetches all pages and returns the complete activity history. Recommended when thorough analysis is needed.
repositoryYesRepository slug containing the pull request.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.0.1
    • addedInput schema / properties / fetchAll
      Added value: +{
+  "description": "When true, fetches all pages and returns the complete activity history. Recommended when thorough analysis is needed.",
+  "type": "boolean"
+}
    • addedInput schema / properties / limit
      Added value: +{
+  "description": "Maximum number of activities to return per page (default: 25, max: 100).",
+  "type": "number"
+}
    • addedInput schema / properties / start
      Added value: +{
+  "description": "Page offset (0-based). Use nextPageStart from a previous response to fetch the next page.",
+  "type": "number"
+}
  2. First observedv1.0.0

TDQS

B3.1/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full behavioral burden. It claims "Retrieve all activities," which conflicts with the schema's default pagination (limit 25, nextPageStart-style paging) and it never mentions the fetchAll flag's role in actually retrieving everything — a materially misleading omission for this tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with the core purpose. The second sentence largely restates the first ("complete activity history and timeline" repeats "all activities... timeline events"), so it does not fully earn its place, but there is no padding beyond that.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 6-parameter, paginated read tool with no annotations and no output schema, the description covers the what but not the how: no pagination behavior, no note on what a returned activity looks like, and no guidance on fetchAll versus manual paging. Minimum viable but with clear gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so every parameter (prId, limit, start, project, fetchAll, repository) is already documented in the schema. The description adds no syntax, default, or paging detail beyond that, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (Retrieve) and resource (activities for a pull request) and enumerates the event types covered: comments, reviews, commits, and other timeline events. This implicitly positions it as the aggregate view over get_comments, get_reviews, and list_commits, though it never names those siblings explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

"Use this to get the complete activity history and timeline" gives implied usage context, but there is no when-not guidance and no mention of the obvious alternatives (get_comments, get_reviews, list_commits) that return subsets of the same data. An agent must infer the choice.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools