Skip to main content
Glama
tugudush
by tugudush

bb_search_repositories

Search repositories in a workspace by name or description, using server-side filtering to find matches across all pages. Supports sorting and pagination.

Instructions

Search for repositories within a workspace by name or description. Uses Bitbucket server-side filtering to search across all repositories, not just the first page. Supports sorting with the sort parameter.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number for pagination
sortNoSort field, e.g. "-updated_on" for newest first, "name" for alphabetical. Prefix with "-" for descending order.
queryYesSearch query to filter repositories by name or description. Uses Bitbucket server-side filtering (BBQL) to search across all repositories in the workspace.
filterNoJMESPath expression to filter/transform structured response data. Applied before format conversion. Example: "values[].{name: full_name, lang: language}" — see https://jmespath.org for syntax
pagelenNoNumber of items per page (max 100). Defaults to 100 for search.
workspaceYesThe workspace or username to search in
output_formatNoResponse format: "text" (default, human-readable), "json" (structured JSON), or "toon" (Token-Oriented Object Notation — compact tabular format that reduces LLM token consumption by 30-60%)
Behavior3/5

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

No annotations are provided, so the description carries the transparency burden. It discloses that it searches across all repositories (not just the first page) and supports sorting, but does not mention read-only nature, authentication, or pagination behavior beyond the schema.

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

Conciseness5/5

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

Three sentences, front-loaded with the main purpose, and every sentence adds value without redundancy or fluff.

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

Completeness4/5

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

Given the moderate complexity and no output schema, the description covers the core behavior (search, all repositories, sorting) and relies on the schema for pagination and filtering details. It could mention the response format but is reasonably complete.

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 the baseline is 3. The description adds no additional parameter meaning beyond what the schema already provides for all seven parameters.

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

Purpose5/5

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

The description uses the specific verb 'Search for' with a clear resource ('repositories within a workspace') and modifiers ('by name or description'), clearly distinguishing it from listing or code search tools.

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?

The description implies usage for finding repositories by name/description and mentions server-side filtering across all repositories, but it does not explicitly name alternatives or state when not to use this tool versus list or code search.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/tugudush/bitbucket-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server