Tencent Ad MCP Server

oauth_get_authorize_url

Generate an OAuth authorize URL for Tencent Ads API account authorization. Provide a redirect URI and optional state parameter to initiate the OAuth flow.

Instructions

获取 OAuth 授权链接 (Get OAuth authorize URL)

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "redirect_uri": "<redirect_uri>"
    },
    "name": "oauth_get_authorize_url"
  }
}

Input Schema

Name	Required	Description	Default
`state`	No	自定义 state 参数
`redirect_uri`	Yes	回调地址

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 30, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations are provided, so the description must fully disclose behavior. It only says 'get' which implies a read operation, but generating an OAuth URL may involve state or configuration. Missing details on side effects, authentication requirements, or return format.

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

Conciseness4/5

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

The description is very concise (one bilingual phrase). It is front-loaded but could include more utility without being verbose. Loses a point for being overly minimal.

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?

Given no output schema and no annotations, the description is insufficient. It does not explain that the tool returns a URL, nor its role in the OAuth sequence. Missing behavioral and flow context.

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 coverage is 100% with both parameters (state, redirect_uri) having descriptions. The description adds no additional meaning beyond the schema, meeting baseline expectations.

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's purpose: '获取 OAuth 授权链接 (Get OAuth authorize URL)'. It is specific with verb+resource and distinguishes from sibling OAuth tools like oauth_refresh_token and oauth_exchange_code.

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 usage guidelines provided. The description does not specify when to use this tool vs. alternatives like oauth_refresh_token or oauth_exchange_code, nor does it mention prerequisites or order in the OAuth flow.

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