Skip to main content
Glama

list_project_versions

Retrieve a list of all versions for a Document360 project to manage content revisions.

Instructions

List all project versions from Document360

Args: ctx: MCP context for logging and error handling

Returns: List of project versions

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The actual handler function that executes the 'list_project_versions' tool logic. It calls client.list_project_versions() and returns the result with logging.
    async def list_project_versions(ctx: Context) -> Dict[str, Any]:
        """List all project versions from Document360
        
        Args:
            ctx: MCP context for logging and error handling
            
        Returns:
            List of project versions from Document360 API
        """
        try:
            await ctx.info("Listing all project versions")
            result = await client.list_project_versions()
            await ctx.info(f"Found {len(result.get('data', []))} project versions")
            return result
        except Document360APIError as e:
            await ctx.error(f"Document360 API error: {e.message}")
            raise e
        except Exception as e:
            await ctx.error(f"Unexpected error listing project versions: {str(e)}")
            raise e
  • server.py:105-115 (registration)
    Registration of the 'list_project_versions' tool with FastMCP via @mcp.tool decorator. Delegates to tools.list_project_versions(ctx).
    @mcp.tool
    async def list_project_versions(ctx: Context) -> dict:
        """List all project versions from Document360
    
        Args:
            ctx: MCP context for logging and error handling
    
        Returns:
            List of project versions
        """
        return await tools.list_project_versions(ctx)
  • The API client helper that makes the actual HTTP GET request to /v2/ProjectVersions endpoint.
    async def list_project_versions(self) -> Dict[str, Any]:
        """Get list of all project versions"""
        return await self._request("GET", "/ProjectVersions")
  • The tool's schema/type signature defined at registration. No input parameters required; returns a dict.
    @mcp.tool
    async def list_project_versions(ctx: Context) -> dict:
        """List all project versions from Document360
    
        Args:
            ctx: MCP context for logging and error handling
    
        Returns:
            List of project versions
        """
Behavior2/5

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

The description lacks behavioral details beyond the basic operation. No annotations are provided, so the description should cover aspects like pagination, ordering, or side effects, but it does not. 'List all project versions' is vague and does not disclose limits or data volume.

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?

The description is very concise with two sentences, but it could be slightly more informative without being verbose. It is front-loaded with the core purpose.

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?

Given no parameters and existence of an output schema, the description is minimally adequate. However, it does not explain what constitutes a 'project version' or any limitations, leaving gaps for an AI agent to interpret.

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?

The input schema has zero parameters, so schema coverage is 100% already. The description adds no parameter info, but baseline for 0 parameters is 4. It mentions 'ctx' (likely implicit) but adds no value beyond the schema.

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 clearly states 'List all project versions from Document360', which is a specific verb ('list') and resource ('project versions'). It distinguishes itself from sibling tools like 'get_article' or 'search_in_project', which operate on different entities.

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. There is no mention of prerequisites, exclusions, or appropriate contexts. The description only states what the tool does.

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/druellan/document360-mcp'

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