Skip to main content
Glama
mdtahmidhossain

jenkins-http-mcp-server

jenkins_get_queue_item

Retrieve a specific Jenkins queue item by its ID to inspect its details and status.

Instructions

Get one Jenkins queue item by ID.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
item_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler function for jenkins_get_queue_item tool. Makes a GET request to queue/item/{item_id} Jenkins API endpoint.
    @mcp.tool()
    def jenkins_get_queue_item(item_id: int) -> dict[str, Any]:
        """Get one Jenkins queue item by ID."""
        return _run(lambda: _get_json(f"queue/item/{item_id}"))
  • Tool is registered via @mcp.tool() decorator within register_tools() function.
    @mcp.tool()
    def jenkins_get_queue_item(item_id: int) -> dict[str, Any]:
        """Get one Jenkins queue item by ID."""
        return _run(lambda: _get_json(f"queue/item/{item_id}"))
  • _get_json helper used by the handler to make the actual HTTP GET request via JenkinsClient.
    def _get_json(path: str, params: dict[str, Any] | None = None) -> Any:
        with _client() as client:
            return client.get_json(path, params=params)
  • _run helper wraps the handler call with error handling, returning ok/data or error dict.
    def _run(fn):
        try:
            return _ok(fn())
        except JenkinsMCPError as exc:
            return exc.to_dict()
  • Tool name listed in READ_ONLY_TOOLS list indicating it's a read-only tool with no write permissions required.
    "jenkins_get_queue_item",
Behavior2/5

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

No annotations provided. The description does not disclose any behavioral traits beyond retrieval, such as read-only nature, side effects, or rate limits. With no annotations, the description carries the full burden but fails to provide safety context.

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

Conciseness4/5

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

Single sentence, no unnecessary words. Front-loaded with action and resource. However, it is minimally informative, which slightly reduces conciseness effectiveness.

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 the tool has an output schema, return values are partially covered. However, missing context: this is a read operation, should be safe to use, and how it relates to listing queue items. No mention of error scenarios or behavior when item not found.

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?

The description mentions 'by ID' but does not add meaning beyond the schema's 'item_id' field. Schema coverage is 0%, but the parameter is self-explanatory. Still, the description does not elaborate on format or constraints.

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 clearly states the tool retrieves a single queue item by ID. It distinguishes from the sibling tool 'jenkins_list_queue' which lists all items, but does not explicitly differentiate from other siblings.

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 on when to use this tool versus alternatives. Implicitly, it is used when an item ID is known, but no mention of prerequisites or when not to use it.

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/mdtahmidhossain/jenkins-http-mcp-server'

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