Skip to main content
Glama
pdfdotco

PDF.co MCP Server

Official
by pdfdotco

wait_job_completion

Poll job status at specified intervals until completion or timeout. Returns final status after job finishes.

Instructions

Wait for a job to complete

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
job_idYesThe ID of the job to get the status of
intervalNoThe interval to check the status of the job (seconds)
timeoutNoThe timeout to wait for the job to complete (seconds)
api_keyNoPDF.co API key. If not provided, will use X_API_KEY environment variable. (Optional)

Implementation Reference

  • The main tool handler for 'wait_job_completion'. It polls job status via _get_job_status in a loop, waiting for 'success' or 'failed' status. It supports configurable interval (default 1s) and timeout (default 300s). Accumulates credits_used across checks.
    @mcp.tool()
    async def wait_job_completion(
        job_id: str = Field(description="The ID of the job to get the status of"),
        interval: int = Field(
            description="The interval to check the status of the job (seconds)", default=1
        ),
        timeout: int = Field(
            description="The timeout to wait for the job to complete (seconds)", default=300
        ),
        api_key: str = Field(
            description="PDF.co API key. If not provided, will use X_API_KEY environment variable. (Optional)",
            default="",
        ),
    ) -> BaseResponse:
        """
        Wait for a job to complete
        """
        start_time = time.time()
        job_check_count = 0
        credits_used = 0
        credits_remaining = 0
        while True:
            response = await _get_job_status(job_id, api_key=api_key)
            job_check_count += 1
            credits_used += response.credits_used or 0
            credits_remaining = response.credits_remaining or 0
            if response.status == "success":
                return BaseResponse(
                    status="success",
                    content=response.content,
                    credits_used=credits_used,
                    credits_remaining=credits_remaining,
                    tips=f"Job check count: {job_check_count}",
                )
            elif response.status == "failed":
                return BaseResponse(
                    status="error",
                    content=response.content,
                    credits_used=credits_used,
                    credits_remaining=credits_remaining,
                )
            await asyncio.sleep(interval)
            if time.time() - start_time > timeout:
                return BaseResponse(
                    status="error",
                    content="Job timed out",
                    credits_used=credits_used,
                    credits_remaining=credits_remaining,
                    tips=f"Job check count: {job_check_count}",
                )
  • Internal helper function that performs the actual API call to POST /v1/job/check to get job status. Used by both wait_job_completion and get_job_check tools.
    async def _get_job_status(job_id: str, api_key: str = "") -> BaseResponse:
        """
        Internal helper function to check job status without MCP tool decoration
        """
        try:
            async with PDFCoClient(api_key=api_key) as client:
                response = await client.post(
                    "/v1/job/check",
                    json={
                        "jobId": job_id,
                    },
                )
                json_data = response.json()
                return BaseResponse(
                    status=json_data["status"],
                    content=json_data,
                    credits_used=json_data.get("credits"),
                    credits_remaining=json_data.get("remainingCredits"),
                    tips="You can download the result if status is success",
                )
        except Exception as e:
            return BaseResponse(
                status="error",
                content=str(e),
            )
  • The BaseResponse model used as the return type for wait_job_completion. Contains status, content, credits_used, credits_remaining, and optional tips.
    class BaseResponse(BaseModel):
        status: str
        content: Any
        credits_used: int | None = None
        credits_remaining: int | None = None
        tips: str | None = None
  • Registration entry point: imports the job module (which triggers @mcp.tool() decorators) and runs the MCP server. The @mcp.tool() decorator on wait_job_completion registers it as a tool.
    def main():
        if len(sys.argv) > 1:
            transport = sys.argv[1]
            if transport == "stdio":
                mcp.run(transport=transport)
            elif transport == "sse":
                if len(sys.argv) < 2:
                    raise ValueError("SSE transport requires a port number")
                port = int(sys.argv[2])
                mcp.run(transport=transport, host="0.0.0.0", port=port)
            elif transport == "streamable-http":
                if len(sys.argv) < 3:
                    raise ValueError(
                        "Streamable HTTP transport requires a port number and path"
                    )
                port = int(sys.argv[2])
                path = sys.argv[3]
                mcp.run(transport=transport, host="0.0.0.0", port=port, path=path)
            else:
                raise ValueError(f"Invalid transport: {transport}")
        else:
            mcp.run(transport="stdio")
    
    
    if __name__ == "__main__":
        main()
Behavior2/5

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

With no annotations, the description fails to disclose blocking behavior, polling mechanism, timeout handling, or return value. It only states the obvious.

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

Conciseness3/5

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

Single sentence is concise but lacks critical information like blocking behavior. It is not optimally informative for an agent.

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?

Description lacks details on return format, polling behavior, error handling, and effect of interval/timeout, leaving significant gaps for a 4-parameter tool.

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?

Input schema has 100% coverage; description adds no extra meaning. Baseline score applies.

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 waits for job completion, but it doesn't differentiate from the sibling 'get_job_check' which likely checks status once.

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 vs alternatives like 'get_job_check'. The description does not provide any usage context.

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/pdfdotco/pdfco-mcp'

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