Skip to main content
Glama

boj_gitlab_list_projects

Retrieve and display your GitLab projects to manage repositories and track development work across your organization.

Instructions

List your GitLab projects

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
per_pageNo

Implementation Reference

  • Handler implementation for the boj_gitlab_list_projects tool which calls the gitlabApiCall utility.
    case "boj_gitlab_list_projects":
      return gitlabApiCall("GET", `/projects?owned=true&per_page=${args.per_page || 20}`);
  • Tool registration within the main tool list definition.
    { name: "boj_gitlab_list_projects", desc: "List your GitLab projects", props: { per_page: { type: "number" } } },
    { name: "boj_gitlab_get_project", desc: "Get a GitLab project", props: { project_id: { type: "string", description: "Project ID or URL-encoded path" } }, req: ["project_id"] },
    { name: "boj_gitlab_create_issue", desc: "Create a GitLab issue", props: { project_id: { type: "string" }, title: { type: "string" }, description: { type: "string" } }, req: ["project_id", "title"] },
    { name: "boj_gitlab_list_issues", desc: "List GitLab project issues", props: { project_id: { type: "string" }, state: { type: "string", enum: ["opened", "closed", "all"] } }, req: ["project_id"] },
    { name: "boj_gitlab_create_mr", desc: "Create a merge request", props: { project_id: { type: "string" }, title: { type: "string" }, source: { type: "string" }, target: { type: "string" } }, req: ["project_id", "title", "source"] },
Behavior2/5

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

With no annotations provided, the description carries full burden but only states the basic action. It lacks details on behavior such as pagination (implied by 'per_page' param), authentication requirements, rate limits, or output format (e.g., list structure, fields returned). This is inadequate for a tool with potential complexity.

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?

The description is a single, efficient sentence with no wasted words. It is front-loaded and directly states the tool's function, making it easy to parse quickly.

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

Completeness2/5

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

Given no annotations, 0% schema coverage, no output schema, and one undocumented parameter, the description is incomplete. It doesn't explain key aspects like how projects are filtered (e.g., by user, visibility), what data is returned, or behavioral constraints, leaving significant gaps for an AI agent.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate but adds no parameter information. The 'per_page' parameter is undocumented in both schema and description, leaving its purpose (e.g., pagination control) unclear. This fails to address the coverage gap.

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?

The description 'List your GitLab projects' clearly states the action (list) and resource (GitLab projects), making the purpose understandable. However, it doesn't differentiate from sibling tools like 'boj_gitlab_get_project' or 'boj_github_list_repos', which would require specifying scope or ownership details.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., authentication), context (e.g., personal vs. group projects), or compare to siblings like 'boj_gitlab_get_project' for single projects or GitHub tools for cross-platform needs.

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/hyperpolymath/boj-server'

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