Skip to main content
Glama

freedom-mcp

by com.getfreedomos

list_segments

List the live lead segment tags for the current company with server-computed lead counts (excluding do-not-contact, archived, and test leads). Segments are the exact comma-separated tokens in crm_leads.source (CSV event imports, website, etc.). Read-only — returns tags and counts only, never lead names/emails. Use when the operator asks which lead segments or event tags exist, or before segment_leads to resolve a loosely-named segment to its exact tag.

Routing: CRM/sales → what lead segments/events exist → use this

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
companyIdYesFreedomOS company id to act within (you must be a member). Required for company-scoped tools.

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description fully discloses read-only nature, exclusion of certain leads, and that it returns only tags and counts. It lacks details on authentication beyond company membership and rate limits, but is fairly transparent.

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?

Concise and well-structured: five sentences covering purpose, data source, read-only nature, usage guidance, and routing. No fluff, front-loaded with key action.

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?

Complete for a simple list tool: one parameter with good schema description, clear return content, exclusions, and relation to sibling. No output schema needed since return type is intuitive.

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?

Only one parameter (companyId) with 100% schema coverage. The schema description already explains it well. The tool description does not add additional semantics beyond what the schema provides, so baseline score applies.

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 it lists live lead segment tags with counts, specifies the exact resource (comma-separated tokens from crm_leads.source), and distinguishes from the sibling tool segment_leads by noting it returns tags and counts only, never lead details.

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?

Explicitly states when to use: 'when the operator asks which lead segments or event tags exist, or before segment_leads to resolve a loosely-named segment to its exact tag.' Provides routing context but does not explicitly list when not to use.

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

All freedom-mcp toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.6/5.0
Disambiguation4/5

The tool set is heavily disambiguated by detailed routing descriptions, domain prefixes, and lifecycle verbs, so most tools have a clear intended purpose. However, at 297 tools there are still close pairs and overlapping decision surfaces (e.g., approval workflows, 'what should I work on' readers, multiple finance/ads readers) that require careful description reading to avoid misselection.

Naming Consistency4/5

Naming is predominantly consistent snake_case verb_noun with strong domain prefixes like shopify_, x_, posthog_, and list_/create_/update_ patterns. Minor inconsistencies exist, such as several collection-returning tools using get_ (get_team_members, get_icps, get_okrs) instead of list_, and some generate_ vs create_ vs draft_ verbs, but the pattern is still predictable overall.

Tool Count1/5

297 tools is an extreme outlier and far beyond a usable MCP tool surface. Even a large suite has no justification for this count in one server; the agent would struggle to select among hundreds of similarly descriptive tools, and the natural 3-15 tool range is exceeded by nearly 20x.

Completeness4/5

The individual domains represented — OKRs, CRM/leads, Shopify, content pipelines, ads, PostHog, team hiring, knowledge, finance, and session management — are covered remarkably well with full lifecycle patterns. Minor gaps exist, such as no full deal CRUD, no delete for several Google/Shopify artifacts, and some analytical surfaces being read-heavy, but most workflows can be completed without dead ends.

Resources