Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
BUILDBETTER_API_KEYYesPersonal API key – generate from BuildBetter dashboard
BUILDBETTER_ENDPOINTNoBuildBetter staging / prod GraphQL endpointhttps://api.buildbetter.app/v1/graphql

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
run-queryB

Execute a read-only GraphQL query

list-typesB

Get a list of available GraphQL object types (excluding internal ones)

build-queryC

Build a simple GraphQL query string for a specific type

schema-overviewA

Return a markdown cheat-sheet describing key schema relationships (mermaid diagram).

search-extractionsC

Search extractions (signals) by keyword/phrase with optional extraction type filter and limit

find-fieldsC

Return the field names for a specified GraphQL type (object or input object)

open-resourceC

Fetch a static resource by URI returned from ListResources

read-resourceB

Alias of open-resource to fetch a static resource by URI

recent-conversation-withC

Find the most recent conversation with a specific person by name

top-customer-issuesC

Get the most common customer issues from extractions/signals

topic-conversationsC

Find conversations discussing a specific topic

query-templateC

Generate a query from predefined templates for common tasks

validate-queryB

Check if a GraphQL query is valid before executing it

nl-queryC

Generate a GraphQL query from a natural language description

helpC

Get help on using BuildBetter MCP effectively

Prompts

Interactive templates invoked by user choice

NameDescription
recent-callsGenerate a GraphQL query to list the most recent calls (interviews)
call-detailsRetrieve detailed information about a specific call by ID
call-transcriptRetrieve the full transcript for a specific call by ID
search-transcriptSearch within a call transcript for a specific phrase
call-extractionsRetrieve extractions (signals) from a call, optionally filtered by type name
signal-frequencyShow how many extractions exist for each extraction type across all calls
feature-requests-by-dateList feature-request extractions across calls in a date range
explore-schemaGuide the user on how to explore the GraphQL schema using available tools/resources
recent-issuesQuery the 20 most recent Issue-type extractions across all calls
feature-requestsQuery the 20 most recent Feature Request extractions
top-customer-issuesShow the most recent Issue-type extractions with the related company name
recent-objectionsList Objection-type extractions in a date range (defaults to last 30 days)
last-call-with-personReturn the most recent call the specified person attended (searches by first name)
context-guideOpen the BuildBetter GraphQL Context Guide resource
top-objectionsAlias for recent-objections (past N days, default 30)
customer-objectionsObjections voiced by customers within a time range (default 30 days)

Resources

Contextual data attached and managed by the client

NameDescription
GraphQL Schema OverviewList of all available object types in the schema.
BuildBetter Context GuideStrategies, query patterns, and best practices for building rich context with BuildBetter GraphQL data.
Schema Relationships Cheat-SheetMarkdown diagram of key entities and how they connect (interview, extraction, extraction_type, joins, person, company).
Common Query ExamplesReady-to-use GraphQL snippets for frequent BuildBetter data tasks.
Practical Query ExamplesReady-to-use examples for the most common scenarios with BuildBetter data

TDQS

B3.1/5.0

Scored across 15 tools

Disambiguation3/5

Most tools have distinct purposes, but there is notable overlap between open-resource and read-resource (which is explicitly an alias), and between build-query, nl-query, and query-template, which all generate queries in different ways, potentially causing confusion. The other tools, like recent-conversation-with and search-extractions, are more clearly differentiated.

Naming Consistency3/5

The naming is mixed, with some tools using verb-noun patterns (e.g., list-types, run-query, validate-query) and others using noun-verb or hyphenated phrases (e.g., schema-overview, top-customer-issues, recent-conversation-with). While readable, the lack of a consistent convention across all tools reduces predictability.

Tool Count4/5

With 15 tools, the count is reasonable for a GraphQL and resource management server, covering query building, execution, validation, and data retrieval. It's slightly on the higher side but still well-scoped, as each tool serves a specific function without obvious redundancy beyond the alias.

Completeness4/5

The toolset covers core GraphQL operations (query building, execution, validation) and resource fetching, with additional utilities for conversation and extraction search. Minor gaps exist, such as no explicit tools for mutations or subscriptions in GraphQL, but agents can likely work around this given the available query-focused tools.