Skip to main content
Glama

PinPinterest — Pinterest Keyword Research

Server Details

Pinterest keyword research from our own crawl: saves, competition, related terms, trends, top pins.

The last two health checks of this connector failed. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.

If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.

Status
Unhealthy
OAuth
Works in Glama
Last Tested
Transport
Streamable HTTP
URL

TDQS

A4/5.0

Scored across 8 tools

Disambiguation4/5

Each tool targets a distinct slice of the domain: single-keyword metrics (keyword_lookup), winning pins for a keyword (keyword_top_pins), winning pins for a niche (niche_top_pins), co-occurring keywords (related_keywords), rising topics (trending), plus two utilities and a queueing call. The only mild overlap is the keyword_top_pins / niche_top_pins / trending cluster, where all three return pin lists and an agent must read the descriptions to pick correctly. That overlap is small and well-explained, so misselection risk is low.

Naming Consistency3/5

All names are snake_case and mostly descriptive, but the conventions are mixed: verb_noun (list_niches, request_keywords), resource-prefixed noun phrases (keyword_lookup, keyword_top_pins, niche_top_pins), and bare/possessive names (trending, my_quota). There is a loose resource-prefix grouping (keyword_*, niche_*) that helps readability, but it is not applied consistently across the set. Readable, not predictable.

Tool Count5/5

Eight tools is well-scoped for a keyword research server: one lookup, three discovery/listing tools, one queueing tool, and two free metadata utilities. No tool looks redundant or like filler, and the surface is small enough for an agent to hold in context.

Completeness4/5

The lifecycle is covered end to end: check a keyword, get winning pins, expand to related keywords, browse niches and trends, queue missing keywords for crawl, and monitor quota. The main gap is the lack of a bulk lookup for several already-tracked keywords in one call, which forces the agent into repeated single-keyword calls (bulk only exists on the request/crawl side). That is a workaroundable inconvenience rather than a dead end.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 8 tool updates
    • First observedkeyword_lookup
    • First observedkeyword_top_pins
    • First observedlist_niches
    • First observedmy_quota
    • First observedniche_top_pins
    • First observedrelated_keywords
    • First observedrequest_keywords
    • First observedtrending

Related MCP Connectors

Related MCP Servers

  • A
    license
    A
    quality
    A
    maintenance
    Free keyword research with live search volume, CPC, competition and 12-month trends.
    11
    11 npm
    MIT
  • A
    license
    A
    quality
    D
    maintenance
    Extracts images, gifs, videos, and search results from Pinterest without authentication. Supports search, pin details, board pins, related pins, autocomplete, and media downloads.
    6
    26 npm
    1
    MIT
  • A
    license
    A
    quality
    C
    maintenance
    Enables agents to plan Pinterest content end to end for digital products: generating pin angles with visual briefs, writing titles and descriptions within Pinterest's character limits, suggesting keyword-named boards, and building a validated bulk-upload scheduling CSV. It also parses pasted Pinterest Analytics exports into totals, top pins, hidden gems, and recommendations — all deterministically, with no login, API key, or posting.
    5
    MIT
  • A
    license
    A
    quality
    A
    maintenance
    Enables AI coding agents to search pins, inspect and preview images, find related pins, read public boards, and download full-resolution originals with no login, API key, or headless browser required.
    6
    166 npm
    MIT
Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources