Skip to main content
Glama
figranium

Figranium MCP Server

Official

task_update

Update an existing Figranium automation task by its task ID to modify actions, schedule, variables, or browser behavior, then apply the changes to keep subsequent runs aligned with current requirements.

Instructions

Update fields of an existing task on the Figranium server.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlNoInitial URL to navigate to when the task starts. Expected type: string. Example: 'https://news.ycombinator.com'
modeNoExecution mode. 'scrape' is fast and headless; 'agent' uses automated browser interaction; 'headful' runs in a visible browser window with human oversight. Expected type: string enum. Example: 'agent'
nameNoDescriptive name of the automation task. Expected type: string. Example: 'HackerNews Scraper'
waitNoStandard delay in seconds to wait after navigation and page loads to let dynamic scripts complete. Expected type: number. Example: 5
taskIdYesThe unique ID of the task to update.
actionsNoSequential list of browser actions/control flow steps to execute. Note: Variable reference MUST use '{$variable_name}' syntax.
stealthNoConfigures realistic stealth, anti-bot, and human behavior simulation on the browser instance.
scheduleNoTask automatic execution schedule. Expected type: object.
selectorNoDefault CSS selector to wait for on the page load before starting actions. Expected type: string. Example: '.main-content'
variablesNoTask variables to store state and dynamic values. Expected type: record object of variable configurations.
descriptionNoDetailed description of what the task automates. Expected type: string. Example: 'Logs in and extracts weekly leads'
humanTypingNoVary typing speeds and insert tiny delays to simulate organic human typing. Expected type: boolean. Example: true
includeHtmlNoWhether to include the raw page HTML in the execution response. Expected type: boolean. Example: false
rotateProxiesNoRotate through configured proxy IPs to prevent IP-based rate limiting. Expected type: boolean. Example: false
rotateViewportNoVary viewport resolutions randomly to simulate multiple desktop and mobile devices. Expected type: boolean. Example: true
disableRecordingNoDisable video/VNC recording of this task to save storage. Expected type: boolean. Example: true
extractionFormatNoTarget export format of any extracted data. Expected type: string enum. Example: 'json'json
extractionScriptNoOptional post-execution script to extract data. Expected type: string. Example: 'return Array.from(document.querySelectorAll("a")).map(el => el.href)'
includeShadowDomNoWhether to parse and resolve target elements residing in Shadow DOMs. Expected type: boolean. Example: true
rotateUserAgentsNoRotate user agents across requests to avoid pattern blocking and fingerprinting. Expected type: boolean. Example: true
statelessExecutionNoIf set to true, clear browser cookies and session states between runs. Expected type: boolean. Example: false
Behavior2/5

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

No annotations exist, so the description carries the full burden, but it only says it updates existing task. It does not disclose whether this is a partial patch or full replacement, what side effects may occur, what happens if the taskId does not exist, or whether the updated task is returned. The schema's testing directive is useful but is not part of the behavioral transparency of the update operation itself.

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?

The description is a single, focused sentence that leads with the action and target resource. It contains no filler and appropriately delegates the extensive field-level detail to the input schema.

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 the large schema and no output schema, the description does not fully clarify expected output, error behavior, or whether omitted fields preserve existing values. However, the exhaustive parameter schema and the integrated post-update testing directive provide substantial context, so the overall definition is adequate but with notable unspecified behavioral aspects.

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?

Schema description coverage is 100%, and every parameter has detailed descriptions, example values, enums, and defaults within the schema. The tool description itself adds minimal parameter meaning, so the baseline of 3 is appropriate.

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 identifies the verb ('Update'), the resource ('fields of an existing task'), and the server context. The phrase 'existing task' differentiates it from create_task, even though the tool does not explicitly name sibling tools.

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?

The description gives clear context about updating an existing task but does not explicitly state when to use it over create_task or when not to use it. The schema-internal directive to execute the task with task_execute after updating adds useful workflow guidance, but the main description does not provide explicit alternatives or 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/figranium/figranium-mcp'

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