// MCP TOOL REFERENCE

PRICEAPI TOOLS

6 tools from the Priceapi MCP Server, categorised by risk level.

READ TOOLS

debug_env_vars Debug tool to check environment variables and current token status. Returns: dict: Environment variable and token information get_job_results Get the results of a finished PriceAPI job to be processed by the user. Args: job_id (str): The job ID to get results for token (str | Non... 2/5 get_status_of_job Get the status of a job from the PriceAPI service. Args: job_id (str): The job ID to check status for token (str | None): Optional PriceAP... 2/5 list_jobs List all jobs for the current API token. Args: token (str | None): Optional PriceAPI token. If not provided, falls back to URL paramet... 2/5

WRITE TOOLS

create_job Create a new PriceAPI job for data collection. Args: source (str): Data source (amazon, ebay, google_shopping, etc.) country (str): Countr... 3/5

EXECUTE TOOLS

wait_for_job_completion Wait for a job to complete and return results. Args: job_id (str): The job ID to wait for token (str | None): Optional PriceAPI token. If ... 4/5

// FAQ

How many tools does the Priceapi MCP server have? +

The Priceapi MCP server exposes 6 tools across 3 categories: Read, Write, Execute.

How do I enforce policies on Priceapi tools? +

Use Intercept, the open-source MCP proxy. Write YAML rules for each tool — rate limits, argument validation, or deny rules — then run Intercept in front of the Priceapi server.

What risk categories do Priceapi tools fall into? +

Priceapi tools are categorised as Read (4), Write (1), Execute (1). Each category has a recommended default policy.

Enforce policies on Priceapi

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept

github.com/policylayer/intercept →