Skip to main content
Glama
kenjihikmatullah

Productboard MCP Server

get_notes

Retrieve notes from Productboard with filtering options for dates, tags, owners, and search terms to access customer feedback and insights.

Instructions

Returns a list of all notes

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
lastNoReturn only notes created since given span of months (m), days (s), or hours (h). E.g. 6m | 10d | 24h | 1h. Cannot be combined with createdFrom, createdTo, dateFrom, or dateTo
createdFromNoReturn only notes created since given date. Cannot be combined with last
createdToNoReturn only notes created before or equal to the given date. Cannot be combined with last
updatedFromNoReturn only notes updated since given date
updatedToNoReturn only notes updated before or equal to the given date
termNoReturn only notes by fulltext search
featureIdNoReturn only notes for specific feature ID or its descendants
companyIdNoReturn only notes for specific company ID
ownerEmailNoReturn only notes owned by a specific owner email
sourceNoReturn only notes from a specific source origin. This is the unique string identifying the external system from which the data came
anyTagNoReturn only notes that have been assigned any of the tags in the array. Cannot be combined with allTags
allTagsNoReturn only notes that have been assigned all of the tags in the array. Cannot be combined with anyTag
pageLimitNoPage limit
pageCursorNoPage cursor to get next page of results
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure but only states the basic action. It doesn't mention pagination behavior (implied by parameters but not described), rate limits, authentication requirements, or what 'all notes' means in context (e.g., access permissions, default ordering). The description adds minimal value beyond the bare function.

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 extremely concise with a single sentence that directly states the tool's purpose. There's no wasted language or unnecessary elaboration, making it front-loaded and efficient for quick understanding.

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

Completeness2/5

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

Given the complexity (14 parameters, no annotations, no output schema), the description is insufficient. It doesn't explain the return format, pagination behavior, or how filtering parameters interact. For a tool with rich filtering options and no structured output documentation, more context is needed to guide effective use.

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 14 parameters with their constraints and mutual exclusivities. The description adds no parameter-specific information beyond what's in the schema, maintaining the baseline score of 3 for adequate but not enhanced parameter semantics.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Returns a list of all notes' states a clear verb ('returns') and resource ('notes'), but it's vague about scope and filtering capabilities. It doesn't distinguish from sibling tools like 'get_note_detail' or explain how it differs from other list tools like 'get_companies' or 'get_features'.

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 on when to use this tool versus alternatives is provided. The description doesn't mention when to use 'get_notes' versus 'get_note_detail' or other sibling list tools, nor does it provide any context about prerequisites or appropriate use cases.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/kenjihikmatullah/productboard-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server