MoveSurge

Trump Truth Social posts

truth_social_posts

Read-only

Recent Truth Social posts by President Trump as they crossed the tape, with available prices before and after the post. Use for 'what has Trump posted today' or 'did his tariff post move markets'.

Input Schema

Name	Required	Description
`hours`	No	Look-back window in hours (1-336, default 24).
`limit`	No	Max results (1-50, default 20).
`query`	No	Free text to match in the post, e.g. tariff.
`end_utc`	No	Exclusive end timestamp with timezone. Overrides the relative look-back window.
`start_utc`	No	Inclusive start timestamp with timezone, e.g. 2026-10-14T00:00:00-04:00.
`with_reaction_only`	No	Only posts with a measured market reaction.

Output Schema

Name	Required	Description	Default
`count`	Yes
`error`	No
`posts`	Yes
`as_of_utc`	No
`data_note`	No
`data_status`	No
`query_window`	No
`window_hours`	No
`withheld_rows`	No
`returned_counts`	No
`newest_result_utc`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedOct 19, 2026

addedInput schema / properties / end_utc

Added value: +{
+  "description": "Exclusive end timestamp with timezone. Overrides the relative look-back window.",
+  "type": "string"
+}

addedInput schema / properties / start_utc

Added value: +{
+  "description": "Inclusive start timestamp with timezone, e.g. 2026-10-14T00:00:00-04:00.",
+  "type": "string"
+}

addedOutput schema / properties / error
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / posts / items / properties / related_companies
```
Added value: +{
+  "type": "object"
+}
```

addedOutput schema / properties / posts / items / properties / screen_matches

Added value: +{
+  "items": {
+    "type": "object"
+  },
+  "type": "array"
+}

addedOutput schema / properties / query_window
```
Added value: +{
+  "type": "object"
+}
```
addedOutput schema / properties / withheld_rows
```
Added value: +{
+  "type": "object"
+}
```

Changed17 schema fields changedOct 18, 2026
- addedOutput schema / properties / as_of_utc
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / properties / data_note
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / properties / data_status
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / properties / newest_result_utc
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
- addedOutput schema / properties / posts / items / properties / market_reaction / properties / instruments / items / properties / baseline_kind
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / properties / posts / items / properties / market_reaction / properties / instruments / items / properties / baseline_utc
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
- addedOutput schema / properties / posts / items / properties / market_reaction / properties / instruments / items / properties / currency
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / properties / posts / items / properties / market_reaction / properties / instruments / items / properties / notes
```
Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
```
- addedOutput schema / properties / posts / items / properties / market_reaction / properties / instruments / items / properties / samples
```
Added value: +{
+  "items": {
+    "properties": {
+      "change_pct": {
+        "type": [
+          "number",
+          "null"
+        ]
+      },
+      "minutes": {
+        "type": "integer"
+      },
+      "price": {
+        "type": [
+          "number",
+          "null"
+        ]
+      },
+      "sample_utc": {
+        "type": [
+          "string",
+          "null"
+        ]
+      }
+    },
+    "type": "object"
+  },
+  "type": "array"
+}
```
- addedOutput schema / properties / posts / items / properties / market_reaction / properties / instruments / items / properties / session
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / properties / posts / items / properties / market_reaction / properties / instruments / items / properties / volume
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / properties / posts / items / properties / market_reaction / properties / interpretation
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / properties / posts / items / properties / price_data_status
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / properties / posts / items / properties / published_et
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
- addedOutput schema / properties / posts / items / properties / read_through
```
Added value: +{
+  "items": {
+    "type": "object"
+  },
+  "type": "array"
+}
```
- addedOutput schema / properties / posts / items / properties / url
```
Added value: +{
+  "format": "uri",
+  "type": "string"
+}
```
- addedOutput schema / properties / returned_counts
```
Added value: +{
+  "type": "object"
+}
```
AddedOct 3, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=false), so the bar is lower. The description still adds real behavioral context: results are anchored to posts 'as they crossed the tape' with prices attached only where 'available', implying a joined dataset with possibly missing price fields rather than raw post text. It does not discuss update latency or pagination, which are the remaining gaps.

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?

Two sentences, no filler. The capability statement comes first and the usage examples follow, so the reader gets the highest-value information up front.

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

Completeness4/5

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

An output schema exists, so return-value explanation is not needed, and the description covers what is fetched and when to use it. Minor omissions remain around data freshness/update cadence and how the relative look-back interacts with the UTC parameters, but nothing blocks correct invocation.

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 all six parameters (hours, limit, query, end_utc, start_utc, with_reaction_only) are already documented in the schema with ranges and formats. The description only implicitly motivates with_reaction_only via 'available prices' and adds no new per-parameter meaning, so the baseline 3 applies.

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

Purpose5/5

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

States a specific resource (Truth Social posts by President Trump) plus the distinguishing payload (prices before and after the post). Nothing in the sibling list (search_headlines, get_article, explained_moves) covers this source, so an agent can route here from the name and first sentence alone.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives two concrete triggering questions ('what has Trump posted today', 'did his tariff post move markets'), which makes the intended use unambiguous. It stops short of naming alternatives (e.g. search_headlines for broader news) or stating when this is the wrong tool, so it is strong context without explicit exclusions.

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

All MoveSurge tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?