Skip to main content
Glama
SartoRiccardo

dataforseo-mcp

ai_chatgpt_llm_responses_task_post

Submit a prompt to an AI model to generate a response, with options for conversation history, web search, and callback notifications.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagNoUser-defined task identifier
top_pNoDiversity of the AI response (0-1, default: 0.92)
priorityNoTask priority: 1 (normal) or 2 (high)
model_nameYesName of the AI model
web_searchNoEnable web search
temperatureNoRandomness of the AI response (0-2, default: 0.94)
user_promptYesPrompt for the AI model
postback_urlNoURL to receive a callback when the task is completed
message_chainNoConversation history
postback_dataNoCustom data to be passed in the callback
system_messageNoInstructions for AI behavior
web_search_cityNoCity name for web search
force_web_searchNoForce AI to use web search
max_output_tokensNoMaximum number of tokens in the AI response
web_search_country_iso_codeNoISO country code for web search

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

D1/5.0
Behavior1/5

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

Tool has no description.

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

Conciseness1/5

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

Tool has no description.

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

Completeness1/5

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

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools