redfin-mcp

Overview Schema Source Related Servers Discussions Admin

Set the active Redfin session

redfin_set_active_session

Idempotent

Set a registered session_id as the active account label for bookkeeping across a conversation. This label does not change which Redfin account requests use.

Instructions

Mark a previously registered session_id as the current account label, for your own bookkeeping across a conversation. The registry is a label only: it does not change which Redfin account requests use. Every redfin tool call goes through whichever browser tab the ContextMint Bridge extension is signed into; to read a different account, sign that tab into it.

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": {
      "session_id": "<session_id>"
    },
    "name": "redfin_set_active_session"
  }
}

Input Schema

Name	Required	Description	Default
`session_id`	Yes	Session id to make active.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv1.0.0Sep 19, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

First observedv0.10.1Jul 29, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Discloses a genuinely non-obvious behavioral fact that annotations cannot convey: the registry is a label only and does not change which Redfin account requests use, with the real switch being the signed-in browser tab. This prevents a costly misconception about auth state. It is consistent with readOnlyHint=false and idempotentHint=true, and adds context beyond them.

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?

Three tight sentences: purpose first, the label-only caveat second, the account-switching workaround last. Every sentence carries information an agent needs; no filler.

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?

For a single-parameter state setter with no output schema and simple annotations, the description covers purpose, the important no-op caveat about account routing, and the alternative path. Nothing required to call it correctly is missing.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds meaning by qualifying the session_id as 'previously registered', telling the agent the id must originate from the registration flow. No format or syntax detail beyond that.

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?

States a specific verb and resource ('Mark a previously registered session_id as the current account label') and immediately scopes it as bookkeeping-only. An agent can distinguish this from the sibling redfin_register_session, which creates the session this tool merely marks active.

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?

Gives a clear condition for use ('previously registered session_id', 'across a conversation') and a corrective path for the adjacent need ('to read a different account, sign that tab into it'). It does not explicitly name redfin_get_session_context or redfin_register_session as alternatives, so it stops short of full when/when-not routing.

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