Fitbit MCP

Get Fitbit OAuth URL

fitbit_get_auth_url

Read-onlyIdempotent

Obtain a Fitbit OAuth authorization URL to connect your account and access health data. Use this when no local token exists.

Instructions

Generate a Fitbit OAuth authorization URL. Use this first when no local token exists.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "fitbit_get_auth_url"
  }
}

Input Schema

Name	Required	Description	Default
`state`	No	Optional OAuth state value generated by the caller.
`scopes`	No	Optional scope override. Defaults to read-only Fitbit scopes used by this server.
`response_format`	No		markdown

Output Schema

Name	Required	Description	Default
`scopes`	Yes
`auth_url`	Yes
`next_step`	Yes
`redirect_uri`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.4.11Jul 30, 2026
Removedv0.4.6Jul 17, 2026
First observedv0.4.5May 26, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, which cover safety and idempotence. The description adds the purpose ('Generate a Fitbit OAuth authorization URL') but does not provide additional behavioral context beyond what annotations convey. No contradictions with 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?

The description is extremely concise with two sentences. The first sentence states the core action, and the second provides a critical usage condition. There is no redundant or extraneous text, and the key information is front-loaded.

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

Completeness4/5

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

Given that an output schema exists (mentioned in context), the description covers the essential: generating the URL and when to use it. It does not detail the redirect flow or token exchange sequence, but for an OAuth URL generation tool, it is reasonably complete for a knowledgeable agent.

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 67% (2 of 3 parameters have schema descriptions). The tool description does not add any parameter-level information; it only states the overall purpose. Since the schema already documents the parameters adequately, the description provides no extra semantic value for parameters.

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?

The description clearly states 'Generate a Fitbit OAuth authorization URL' with a specific verb and resource. It also adds usage context ('Use this first when no local token exists'), which distinguishes it from sibling tools like fitbit_exchange_code that handle the token exchange step.

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

Usage Guidelines4/5

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

The description includes explicit guidance: 'Use this first when no local token exists.' This clearly indicates when to use the tool. However, it does not list alternatives or explicitly state when not to use it beyond the implied condition.

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