Skip to main content
Glama
Sign In
Artsy Analytics MCP Server

Artsy Analytics MCP Server

by damassi
OverviewSchemaRelated ServersDiscussionsAdmin
TypeScript

get_partner_visitor_demographics

get_partner_visitor_demographics

Analyze visitor demographics by device, location, referral source, or landing page for partners. Retrieve data over customizable periods to understand audience insights and optimize engagement strategies.

Instructions

Get visitor demographic breakdowns by device, country, referral source, or landing page

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": {
      "partnerId": "<partnerId>"
    },
    "name": "get_partner_visitor_demographics"
  }
}

Input Schema

NameRequiredDescriptionDefault
firstNoNumber of top results to return
metricNoType of demographic breakdown to retrieveVISITOR_BY_LOCATION
objectTypeNoObject type for the demographic breakdownCOUNTRY
partnerIdYesPartner ID to get visitor demographics for
periodNoTime period for demographic dataFOUR_WEEKS

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations provided, the description carries full burden but only states what the tool does, not how it behaves. It lacks details on permissions, rate limits, data freshness, pagination, or error handling. For a data retrieval tool with 5 parameters, this leaves significant behavioral gaps.

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 a single, efficient sentence that front-loads the core purpose without unnecessary words. Every element (verb, resource, breakdown dimensions) earns its place, making it easy to parse quickly.

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

Completeness3/5

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

Given 5 parameters, no annotations, and no output schema, the description is minimally adequate but incomplete. It covers the what but not the how or when, leaving gaps in behavioral context and usage guidance that could hinder effective tool selection and invocation.

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 100%, so the schema fully documents all 5 parameters. The description adds minimal value by listing breakdown types that correspond to 'metric' and 'objectType' enums, but doesn't explain parameter interactions or semantics beyond what's in the schema.

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 verb 'Get' and the resource 'visitor demographic breakdowns', specifying the breakdown dimensions (device, country, referral source, landing page). It distinguishes from siblings by focusing on demographics rather than activity, sales, or time series, though it doesn't explicitly contrast with them.

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 guidance is provided on when to use this tool versus alternatives like 'get_partner_audience_stats' or 'get_partner_complete_analytics'. The description implies usage for demographic data but doesn't specify prerequisites, exclusions, or comparative contexts with sibling tools.

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

Related Tools