Skip to main content
Glama
damassi

Artsy Analytics MCP Server

by damassi

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
USER_IDYesYour Artsy user ID
X_ACCESS_TOKENYesYour Artsy access token
METAPHYSICS_ENDPOINTYesThe Artsy GraphQL API endpoint

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Server capabilities have not been inspected yet.

Tools

Functions exposed to the LLM to take actions

NameDescription
get_partner_activity_statsB

Get partner activity analytics including pageviews, artwork views, and unique visitors

get_partner_sales_statsC

Get partner sales analytics including order count, revenue, and response times

query_analytics_customC

Execute a custom GraphQL query against the analytics schema

get_partner_artworks_published_statsC

Get partner artwork publishing statistics and trends

get_partner_audience_statsC

Get partner audience analytics including unique visitors, commercial visitors, and geographic data

get_partner_complete_analyticsC

Get comprehensive analytics overview for a partner including all major metrics

get_partner_inquiries_statsB

Get partner inquiry analytics including inquiry count and response times

get_partner_top_artworksB

Get partner's most viewed artworks with ranking data

get_partner_visitor_demographicsB

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

get_partner_time_series_analyticsC

Get time series data for partner analytics with optional cumulative view

get_partner_modern_pageviewsC

Get detailed pageview analytics using the modern pageview schema with time series support

get_partner_top_contentC

Get top-performing content (artworks, shows, artists, or viewing rooms) by views

get_partner_sales_time_seriesC

Get detailed sales analytics with time series data including revenue amounts

get_partner_inquiry_time_seriesC

Get detailed inquiry analytics with time series data and response times

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.3/5.0

Scored across 14 tools

Disambiguation3/5

The tools have clear distinctions in their primary focus areas (activity, artworks, audience, inquiries, sales, time series, top content, demographics, custom queries), but there is notable overlap between some tools. For example, 'get_partner_complete_analytics' overlaps with many others by providing an overview, and 'get_partner_time_series_analytics' overlaps with specific time series tools like 'get_partner_inquiry_time_series' and 'get_partner_sales_time_series'. Descriptions help clarify, but an agent might struggle to choose between overlapping tools for specific needs.

Naming Consistency5/5

All tool names follow a consistent 'get_partner_*_stats' or 'get_partner_*_analytics' pattern, with variations like 'time_series', 'top_artworks', or 'visitor_demographics' fitting logically. The naming is highly predictable and readable, using snake_case uniformly throughout. This consistency makes it easy for an agent to understand the structure and purpose of each tool at a glance.

Tool Count4/5

With 14 tools, the count is reasonable for an analytics server covering various aspects like activity, sales, inquiries, and demographics. It's slightly on the higher side but well-scoped to provide detailed insights without being overwhelming. Each tool appears to serve a specific analytical function, though some redundancy might be present, keeping it within a manageable range for the domain.

Completeness4/5

The tool set covers a broad range of analytics for partners, including activity, audience, inquiries, sales, time series, top content, and demographics, with a custom query option for flexibility. Minor gaps exist, such as no explicit tools for updating or deleting analytics data (which might be intentional if read-only) or more granular filtering options, but the surface is comprehensive for querying and reporting purposes, allowing agents to access most needed metrics.