Skip to main content
Glama
scraperapi

scraperapi-mcp-server

Official

ai_parser_update

Update an existing AI parser by adding, modifying, renaming, or removing fields. Changes to field definitions trigger asynchronous regeneration; renames and removals apply immediately.

Instructions

Edit an AI parser's fields, creating a new version.

    Add, modify, rename, or remove fields. Adding or modifying fields triggers
    asynchronous regeneration (poll 'ai_parser_get_details' until 'FINISHED'); renaming
    or removing fields is applied immediately.

    When to use:
    - Adjusting an existing parser's fields (add/modify/rename/remove) rather
      than recreating it

    When NOT to use:
    - Creating a brand-new parser (use 'ai_parser_create')

    Args:
        params (AiParserUpdateParams): parser_id (required) and optional version,
            plus any of add_fields, modify_fields, rename_fields, remove_fields.

    Returns:
        str: JSON with the parser id and (new) version.

    Raises:
        ToolError: If the API key is missing, the rate limit is exceeded, the
            inputs are invalid, or the request fails.
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

Discloses that add/modify fields trigger asynchronous regeneration (poll 'ai_parser_get_details') while rename/remove apply immediately. No contradiction with annotations (readOnlyHint=false, destructiveHint=false). This adds crucial context beyond annotations.

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?

Well-structured with clear sections (description, when to use/not, args, returns, raises). Every sentence serves a purpose; no fluff. Front-loaded with the core action.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers all essential aspects: purpose, usage context, parameter summary, return value, and error conditions. Output schema exists, so return details are not required. Raises section addresses common failures. Complete for a moderately complex 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?

Despite the input schema containing detailed descriptions for each parameter, the tool's description summarizes the parameters in a concise 'Args' section. It adds value by grouping parameters and clarifying optionality, though the schema already covers individual semantics 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?

Description explicitly states 'Edit an AI parser's fields, creating a new version.' It distinguishes from sibling 'ai_parser_create' by specifying when to use each. Additionally, it enumerates specific operations (add, modify, rename, remove), leaving no ambiguity.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Includes a dedicated 'When to use' and 'When NOT to use' section, directing agents to use 'ai_parser_create' for new parsers. This clearly defines the tool's domain and prevents misuse.

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/scraperapi/scraperapi-mcp'

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