Skip to main content
Glama

get_plugin

Retrieve details of a Jenkins plugin by its short name, including dependencies when depth is set to 2 or higher.

Instructions

Get a specific plugin from Jenkins

Contains detailed information about the plugin, including dependencies when depth >= 2.

Args: short_name: The short name of the plugin depth: The depth of the information to retrieve. Default is 2 (includes dependencies).

Returns: The plugin details, or None if not found

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
short_nameYes
depthNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The MCP tool handler that implements 'get_plugin'. It is decorated with @mcp.tool(tags={'read'}) and calls the REST client's get_plugin method.
    @mcp.tool(tags={'read'})
    async def get_plugin(ctx: Context, short_name: str, depth: int = 2) -> dict | None:
        """Get a specific plugin from Jenkins
    
        Contains detailed information about the plugin, including dependencies when depth >= 2.
    
        Args:
            short_name: The short name of the plugin
            depth: The depth of the information to retrieve. Default is 2 (includes dependencies).
    
        Returns:
            The plugin details, or None if not found
        """
        return jenkins(ctx).get_plugin(short_name=short_name, depth=depth)
  • The REST client helper method that fetches all plugins and filters by short_name to find the specific plugin.
    def get_plugin(self, *, short_name: str, depth: int = 2) -> dict | None:
        """Get a specific plugin by short name.
    
                Args:
                    short_name: The short name of the plugin.
                    depth: The depth of the information to retrieve. Default is 2 (includes dependencies).
    
        Returns:
                    A list of plugins that can be downgraded.
        """
        plugins = self.get_plugins(depth=depth)
        for plugin in plugins:
            if plugin.get('shortName') == short_name:
                return plugin
        return None
  • The MCP server instance and tool registration mechanism. plugin.py is imported here so the @mcp.tool() decorators register get_plugin (and all other plugin tools) with the FastMCP server.
    mcp = JenkinsMCP('mcp-jenkins', lifespan=lifespan)
    
    # Import tool modules to register them with the MCP server
    # This must happen after mcp is created so the @mcp.tool() decorators can reference it
    from mcp_jenkins.server import build, item, node, plugin, queue, view  # noqa: F401, E402
Behavior4/5

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

Despite no annotations, description discloses return type (plugin details or None) and depth behavior. Lacks explicit mention of being read-only or auth needs, but sufficient for a simple get tool.

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?

Succinct two-sentence description plus bullet param/return docs. Every sentence adds value; front-loaded with verb. No waste.

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?

Covers purpose, params, and return clearly. Output schema exists, so return details not needed. Lacks edge cases or prerequisites, but complete for a get tool.

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

Parameters4/5

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

Adds meaning beyond schema: 'short name' context and 'depth' with default and dependency implication. Schema has 0% coverage, so description compensates well.

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?

Clearly states 'Get a specific plugin from Jenkins' with 'detailed information' and 'dependencies'. Distinguishes from siblings like get_all_plugins (list) and get_plugin_dependency_graph (graph).

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?

Implies usage when needing plugin details with dependencies via depth parameter, but lacks explicit guidance on when to use vs alternatives like get_plugin_dependency_graph or cues for exclusions.

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/lanbaoshen/mcp-jenkins'

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