rapidapi
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
| Name | Description |
|---|---|
| get_user_recent_tweetsD | – |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool's purpose is clearly defined as retrieving recent tweets for a user, leaving no room for confusion or misselection.
The tool name 'get_user_recent_tweets' follows a consistent verb_noun pattern (get + user_recent_tweets), and since there is only one tool, there is no inconsistency to evaluate. The naming is clear and predictable.
A single tool for a server named 'rapidapi' suggests a severely limited scope, as APIs typically offer multiple endpoints for various operations. This feels too thin and underpowered for any meaningful domain coverage, indicating a poor fit for typical agent workflows.
The server appears to target Twitter or social media data, but with only one tool to get recent tweets, it lacks any other operations like posting tweets, searching, managing users, or handling other API functions. This is severely incomplete for the implied domain, leaving major gaps that will hinder agent tasks.